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?

We should add a compile-time check when trying to use extern in an unsupported manner.
For example extern cannot be used in val foo: Int = extern
Also, it should report usages as a default parameter of methods, if it is not runtime exceptions should contain information about unsupported usage of the extern method.

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",
"

COMMUNITY-DRIVEN WORK TRACKING ISSUE

Summary of feature

Today, Silk.NET has no official support for receiving KeyDown (et al) events in any keyboard layout other than US (even though the SDL backend accidentally mandatorily supports it, but this is a bug with that backend).

This has been requested lots of times, and even got to a point where [a proposal made it to review](https://gi