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?

https://github.com/scala-native/scala-native/blob/126c9d3ab5874edf15173ad25eb0633b66b0f732/docs/user/testing.rst

official documentation say follows

libraryDependencies += "org.scala-native" %%% "junit-runtime" % |release|
addCompilerPlugin("org.scala-native" % "junit-plugin" % |release| cross CrossVersion.full)

but this add Compile scope dependency 😢

• https://gith

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