Update to upstream tinywl

[shtirlic]

• Use Scene Graph for rendering
• Use golang container/list for toplevels
• Follow upstream implementation as close as possible
• Include all upstream comments to the code
• Add more upstream protocol methods to go-wlroots lib
• Separate wlroots API to the same structure as upstream
• Use slog for logging (tint will be used when fixed in upstream Fields names are not printed for C structures lmittmann/tint#55)
• Closes Poorly comented #17

[nbsp]

looks good ^^ i was actually working on this same PR idea :)
just a nitpick but the rest seems nice

[nbsp]

also, maybe split this to a few atomic commits (if that's even possible at this scale)? thinking about wlroots' contributing guide:

This means that every commit should be small, digestible, stand-alone, and functional.

[shtirlic]

also, maybe split this to a few atomic commits (if that's even possible at this scale)? thinking about wlroots' contributing guide:

This means that every commit should be small, digestible, stand-alone, and functional.

True, but not this time unfortunately, after this PR get merged, the changes can be done it fractional commits.

[shtirlic]

@alexbakker did you have a chance to look ?

[shtirlic]

ping @alexbakker , is there are anything I can do more for this PR ?

[alexbakker]

This does much more than just "update to upstream tinywl" 😉.

Anyway, LGTM.

[shtirlic]

yes, sorry for that, in future I will be more precise.