@flyx please review

Thanks for contributing!

I think the more future-proof solution would be to just always use move, which I suppose should suffice to get the compiler to not deep-copy strings. However documentation of the stdlib is still lacking, so I am not entirely sure on this. Give me a day or two to dig around and test.

Thanks for contributing!

I think the more future-proof solution would be to just always use move, which I suppose should suffice to get the compiler to not deep-copy strings. However documentation of the stdlib is still lacking, so I am not entirely sure on this. Give me a day or two to dig around and test.

How about use when(compiles)?

  when compiles(shallowCopy(start, ctx.input.next())):
    shallowCopy(start, ctx.input.next())
  else:
    start = ctx.input.next()

Yeah, the compiles solution would do. Can you modify your PR to do this? ideally with a comment that it's for the different GC mechanisms.

Yeah, the compiles solution would do. Can you modify your PR to do this? ideally with a comment that it's for the different GC mechanisms.

sure, done. @flyx pls review

Merged, thanks! Sorry for the delay.

Since this prevents people from using the lib, I tagged release 2.2.1 to incorporate this fix. CI has problems with it but that's because GitHub did a booboo; I ensured locally that it works on macOS.

awesome. thx