Add support for variable-width bytes in the IR

[tybug]

Many changes here were analogous to strings, and I've unified approaches where it made sense.

[tybug]

I forgot to mention that unfortunately this is a breaking change for alternative backends/providers, as we're changing the provider interface. We could maybe add a dynamic overload based on kwargs on our end if we think it's worthwhile? We'll have to contend with this again when/if we add width to draw_float, which is maybe a good argument for adding it to the interface now with a constant value of 64.

(cc @pschanely: this pr changes draw_bytes from size: int to min_size: int, max_size: Optional[int]).

[Zac-HD]

Breaking changes are entirely fine at this point; backends are explicitly unstable and we've warned known downstream both generally in advance and now about this PR. (feels polite to make it a minor release though)

Overall looks great; I'd expect to merge with only minor changes.

[tybug]

Breaking changes are entirely fine at this point

That's what I was hoping to hear 😄. Agree with changing to a minor release 👍. Will return to this pull within a few days.

[tybug]

(a few days...or now 🙂)

@pschanely the interface is now:

def draw_string(
    self,
    intervals: IntervalSet,
    *,
    min_size: int = 0,
    max_size: int = COLLECTION_DEFAULT_MAX_SIZE,
    forced: Optional[str] = None,
    fake_forced: bool = False,
) -> str:

def draw_bytes(
    self,
    min_size: int = 0,
    max_size: int = COLLECTION_DEFAULT_MAX_SIZE,
    *,
    forced: Optional[bytes] = None,
    fake_forced: bool = False,
) -> bytes:

noting that draw_string no longer accepts max_size: int | None.

Of course, you're free to change the default for max_size here – otherwise, you can access it at from hypothesis.internal.conjecture.data import COLLECTION_DEFAULT_MAX_SIZE.

[pschanely]

(a few days...or now 🙂)

@pschanely the interface is now: [...]

Acknowledged!

[Zac-HD]

Looks sweet, let's ship it!