.ruby
.ruby
yea @mhermier I've been experimenting with it in luxe for a while looking for edge cases in daily use, I think there's value in reducing friction for the 99% when...
often you want resilience as well as information, which this PR aims for.
This is not resilient: > let the fiber kill your program
nextToken is called twice, which copies next -> current and current -> previous so both should be set but there's no particular reason I didn't initialize them. It'd make sense...
I already said it's better to initialize them explicitly, which will happen soon, don't worry about your files on your PC until then (hyperbole doesn't make a point stronger in...
hey @trufae thanks for the PR, if you check the build failures on the CI above, you'll notice there's an issue in your proposed change when both OPT and META...
I'm most curious on the use case here like what do you want those bits for? in particular since we have WrenHandle it seems to overlap with, the use case...
Nothing on the compilation process has changed at this time so the above discussion is where it's at for now.
I'll look at it closer soon (we moved house during Feb so been mostly afk). I'm curious, since you say expedite, is it an issue you're running into very frequently...
Side note: That's true for any breaking change @ChayimFriedman2 this one is no different or worse.