Komari Spaghetti
Komari Spaghetti
Ops, looked at this but forgot to respond. Isn't this just quirk of floating point numbers. Not really much this lib can do about that.
> Is it possible to: not provide `len_hint` if a given type is some float? Not sure what you mean. Do you mean that `range` should not provide `len_hint` for...
I see. Yea, both of these sounds good to be :+1:
Hmmmmm. How about: ```zig pub fn range(comptime T: type, start: T, end: T, opts: struct { inclusive: bool = false, step: T = 1 }) Range(T) { return .{ .start...
> What will happen for `range(u8, 0, 255, .{ .step = 2 });`? Well, that would overflow with the current behavior. We could have an implementation that handles this, which...
As of 0c2a668c31b20ffefcaa8e59f70f85b8df94eccb, `ziter.range` no longer supports floats and `step` has been removed in favor of: ```zig ziter.range(u8, 0, 10) .step_by(2) ```
This is not a feature this library has yet and I've not had much motivation to implement this feature myself. It is not really a feature I need this library...
I've tried your code and it does compile fine (after changing `.int = clap.parsers.int,` to `.int = clap.parsers.int(u8, 10),`). The problem now is when you do: ``` $ zig-out/bin/exe client...
Haven't tried to building this project in over a year and Zig has done some changes in that time. No wonder it doesn't build. Anyway, I'm not really sure I...
Yea, this is a quite common problem when writing parsers called Left Recursion. You basically have the rule: ``` expr = binOp binOp = expr + expr ``` So what...