Daniel Grießhaber
Daniel Grießhaber
Thanks for your comments, > Currently these are indistinguishable from normal strings, so cosegen emitting braces or json generation become needlessly difficult. Good point. I did not think about this....
I just pushed a new commit that implements the proposed `"This is ${interpolated}"` syntax that got the most upvotes on discord. I'm still happy to get any suggestions on the...
Just implemented support in the interpreter: ``` > let foo = 42 > "The answer is ${foo:o} in octal" = "The answer is 52 in octal" ```
> Can you squash your commits? Sure, done :) > Can it handle `"${ "${ 0 }" }"` (nested interpolated strings)? No, but I'm also honestly not sure how you...
> but to me this seems like a more robust way of parsing anyway. Well, I need to refactor the lexing & parsing anyway, so I will give it a...
I just did a refactor of the lexing & parsing steps. Notable changes: - Parsing now supports nested interpolated strings (`"${ "${ 0 }" }"`) which isn't something you should...
> You have a typo in your commit message: "forat" Thanks, fixed
I added syntax highlighting support in the vscode extension just now. Other editors are not yet supported and just render interpolated blocks as part of the string but that's at...
Hi jt, I just started a 2 week vacation so I won’t be able to work on this immediately. > "{foo} bar" should always just be a string well it...
Your right, fair point. I thought about the tagged strings again, if we would allow any comptime function it would probably make sense to also support any return value, then...