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

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.

Implement Suggestion

https://github.com/burtonageo/cargo-bundle/pull/93/files

For macos:

        // TOD

Summary of feature

Math library has 2D and 3D common shape types like Ray2D, Ray3D, Cube, Sphere, etc

It could be useful to have Ray2D and Ray3D to have methods to return the intesection with shapes and volumes.

Also, test methods to get whether shapes and volumens overlap.

Comments

Area/volume overlapping is a very common practice for graphics development in areas like frutum c