/**
     * Gets the replacement string for colons in URLs.
     *
     * @return the colon replacement string
     */
    public String getColonStr() {
        return colonStr;
    }

    /**
     * Sets the replacement string for colons in URLs.
     *
     * @param colonStr the colon replacement string to set
     */
    public void setColonStr(final String colonStr) {
        this.colonStr = colonStr;
    }

User-agent: GoodBot
Disallow: /admin/
InvalidDirective: some-value
unknown-field: test
Disallow /missing-colon
Disallow:    # empty value (should be treated as allowing all)
Allow: /public/
Crawl-delay: invalid-number
Crawl-delay: -10
Crawl-delay: 5.5
Crawl-delay:
Allow:    # empty value

# Case 3: Multiple colons in directive
User-agent: MultiColonBot
Disallow: http://example.com:8080/path
Allow: /path:with:colons

 * information on "bogons", including lists of IPv6 bogon space, see:
 *
 * <ul>
 *   <li><a target="_parent"
 *       href="http://en.wikipedia.org/wiki/Bogon_filtering">http://en.wikipedia.
 *       org/wiki/Bogon_filtering</a>
 *   <li><a target="_parent"
 *       href="http://www.cymru.com/Bogons/ipv6.txt">http://www.cymru.com/Bogons/ ipv6.txt</a>

Go 1.26 added a new `urlstrictcolons` setting that controls whether `net/url.Parse`
allows malformed hostnames containing colons outside of a bracketed IPv6 address.
The default `urlstrictcolons=1` rejects URLs such as `http://localhost:1:2` or `http://::1/`.
Colons are permitted as part of a bracketed IPv6 address, such as `http://[::1]/`.

Go 1.26 enabled two additional post-quantum key exchange mechanisms:

        // Invalid number should be ignored, valid ones should work
        assertEquals(0, robotsTxt.getCrawlDelay("GoodBot")); // invalid values ignored

        // Test MultiColonBot - colons in paths should be preserved
        assertFalse(robotsTxt.allows("http://example.com:8080/path", "MultiColonBot"));
        assertTrue(robotsTxt.allows("/path:with:colons", "MultiColonBot"));

That is not the same as declaring default values like would be with:

```Python
    first_name="john", last_name="doe"
```

It's a different thing.

We are using colons (`:`), not equals (`=`).

And adding type hints normally doesn't change what happens from what would happen without them.

But now, imagine you are again in the middle of creating that function, but with type hints.

 * information on "bogons", including lists of IPv6 bogon space, see:
 *
 * <ul>
 *   <li><a target="_parent"
 *       href="http://en.wikipedia.org/wiki/Bogon_filtering">http://en.wikipedia.
 *       org/wiki/Bogon_filtering</a>
 *   <li><a target="_parent"
 *       href="http://www.cymru.com/Bogons/ipv6.txt">http://www.cymru.com/Bogons/ ipv6.txt</a>

    assertThat(parse("http://[::1]/").host).isEqualTo("::1")

    // ... but they're included in toString().
    assertThat(parse("http://[::1]/").toString()).isEqualTo("http://[::1]/")

    // IPv6 colons don't interfere with port numbers or passwords.
    assertThat(parse("http://[::1]:8080/").port).isEqualTo(8080)
    assertThat(parse("http://user:password@[::1]/").password).isEqualTo("password")

		if IsTerminal() {
			return color.New(color.FgRed, color.Bold).SprintFunc()
		}
		return fmt.Sprint
	}()

	RedBoldf = func() func(format string, a ...any) string {
		if IsTerminal() {
			return color.New(color.FgRed, color.Bold).SprintfFunc()
		}
		return fmt.Sprintf
	}()

	Red = func() func(format string, a ...any) string {
		if IsTerminal() {
			return color.New(color.FgRed).SprintfFunc()
		}

Christoph Obexer <******@****.***> 1749718797 +0200