Felix Queißner

> This degrades the initial UX because it looks like you have to manually set the stack size. Is there any reason to distinguish between stack and heap anyways since...

> Hey, I was looking at this code, I found that changing the io mode to blocking eliminates the error and might be ok for the sake of the example,...

> I added this to the accept method, keeping the original async example, this worked. However, I am not so sure if this fits well. I would happily open a...

I don't think it's possible to do so yet, xtensa isn't a supported platform by Zig/LLVM yet. I think you have to reimplement the parsing and rendering for Xtensa platform

This looks promising! Before i merge this i wanna make sure that i can run the benchmarks with the new version as well. First thing i noticed: It doesn't do...

> Yes, editing is enabled. Okay, cool. I fixed two bugs in the text generation so i can actually convert to text format. I would keep it that way until...

@raeleus what renderer do you use? `svg2tvgt` doesn't do any cropping, so it looks like your renderer is actually not clipping the final result to `(0, 0)` to (5, 5)`...

I found another SVG file that converts to an invalid result: ```svg ``` This is rendered as  while the correct output (generated by the old .NET tool) looks like...

> Can you provide a textual/lisp output of the .Net version? usvg is definitely correct here, meaning I'm writing curves wrong. Sure! settings.tvgt ``` (tvg 1 (24 24 1/1024 u8888...

> I've converted the produced tvgt to SVG by hand and it looks perfectly fine. So the data is correct. Maybe I misunderstood the spec somewhere? The arc definition has...