WIP fix: Align @geometry with main

[cieplypolar]

• wgsl resolution test for lines combinations example (tricky, because there are a lot of options)

Closes #1930.

[github-actions]

pkg.pr.new

packages
Ready to be installed by your favorite package manager ⬇️

https://pkg.pr.new/software-mansion/TypeGPU/typegpu@582630b4069c4b7d3b05d6148aac3876728dfed0

https://pkg.pr.new/software-mansion/TypeGPU/@typegpu/noise@582630b4069c4b7d3b05d6148aac3876728dfed0

https://pkg.pr.new/software-mansion/TypeGPU/unplugin-typegpu@582630b4069c4b7d3b05d6148aac3876728dfed0

benchmark
view benchmark

commit
view commit

[aleksanderkatan]

Nice!

Do we plan on keeping these examples as dev only?

[aleksanderkatan]

This does not look intended, did it look like this before the example stopped working?

Also, the last two test cases disappear when the segment becomes too short.

[deluksic]

Yeah, I know about these issues. I have this new PR open which rewrites the implementation, then I'll think about what to do in these specific cases. It is not completely obvious to me what strategy is visually best yet.

[deluksic]

oh wait, this exact issue I have not seen before. But maybe look at the new implementation PR and see if you can rebase your changes. I have already aligned (all?) the implementations with recent main.

[deluksic]

I had another look, and indeed this happens when you try using "arrow" caps. They are kinda fiddly in terms of cases where they work nicely. When there is such a short and thick segment, the arrow is way bigger than it, causing the issue you are seeing. So in this case, yes it is expected.

[iwoplaza]

Do we plan on keeping these examples as dev only?

Yes, until we publish the @typegpu/geometry package.

[deluksic]

@cieplypolar Please let me know if there are more things to align in #1935, otherwise we can close this one.

EDIT: didn't realize there were tests. I will move them over to the other PR.