Not a big deal, but I noticed a ton of trailing whitespaces on the repo code, so it would be nice to remove them with a linter or similar!

Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

Specific Demand

When resolving assets, we should determine of the current program is contained within a bundle. If it is, then we should cananocalize the asset differently to be relative to the .app/.deb/.rpm/.exe for a smoother distribution experience.

• macOS

These targets do not provide a straightforward way of bundling assets. I've opted to make it the asset dir configu

The code in question should be here.
https://github.com/scala-native/scala-native/blob/63d07093f6d0a6e9de28cd8f9fb6bc1d6596c6ec/test-interface/src/main/scala/scala/scalanative/testinterface/signalhandling/SignalConfig.scala#L45-L71

Potential idea for a fix.
https://stackoverflow.com/questions/16509614/signal-number-to-name

When use "$: react-native dom"
Appears:
No version of 'react-native-dom' found that satisfies a peer dependency on 'react-native@0.56.0'

This is my package.json:

{
"name": "dom",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"test": "jest"
},
"dependencies": {
"react": "16.4.1",
"

Summary

After closing a GLFW rendering window GLFW ande some referenced objects remain in memory.

Steps to reproduce

• Platform: Desktop
• Framework Version: .NET 5
• API: OpenGL

1. Run the code from 'Tutorial 1.1 - Hello Window' in the debugger with a breakpoint on the closing brace of Main.
2. Once the breakpoint is hit create a memory snapshot and open it.
3. Inspecting the snapsh

https://github.com/metalbear-co/mirrord/blob/main/mirrord-layer/src/lib.rs#L63

The shared library constructor has two unwraps in it, it would be nicer if we could just print to stderr and exit gracefully instead of rust panic.