Toomas Vooglaid
Toomas Vooglaid
I disagree. First `collect` creates the top collection block. Everything else collected/kept should be included in this block. Each new `collect` creates a new collection block that will be included...
And it is consistent with [docs](https://github.com/red/docs/blob/master/en/parse.adoc#393-collect): > First use of collect allocates a new block that is returned by parse function, any subsequent collect allocates at the tail of its...
IMO, the syntax above is not incorrect *per se*, it is incorrect for given purpose/expectation.
I may have missed the discussion of it but if `/` is changed into float division and `//` is not changed into integer division, then ~all the code that currently...
> because that's what people *expect* If that's the main argument then there should be looots of breaking changes ahead :) @greggirwin How about allowing truncated floats for loop-limits?
Nitpicking: strictly speaking, you can't go "away from infinity" on number line; always towards infinity. I support existing solution.
`pair!` is good for picking points from image
Ok, thanks!
@qtxie Good, thank you!
Just to return `trim reduce [dir pos]` from current `split-path` would be non-breaking, logically sound, and would round-trip with `rejoin`.