Pierre Krieger
Pierre Krieger
The question is: how will README interact with the Cargo registry? Currently the examples are in the README file mainly because it's easy to read when you discover a library...
That's out of scope of a FFI library in my opinion.
As far as I know, the `-sys` suffix is for libraries that somehow link to a native library (plus contains the FFI). There's no indication whether or not it should...
To be more precise, it's a bug with the version of glfw included in glfw-sys, not glfw-sys.
Ah, so it's good. It should be possible to remove this line then: https://github.com/PistonDevelopers/glutin_window/blob/master/src/lib.rs#L66 ..and remove the dependency to `gl-rs`
I would suggest to address any question or problem that you might face by opening issues or discussions in the spec repo (https://github.com/paritytech/json-rpc-interface-spec/).
For my bluetooth experiments, I went for `/bluetooth/xx:xx:xx:xx:xx/l2cap/2/rfcomm/N` (where the `xx` thing is the BD_ADDR and `N` is the RFCOMM port).
I think that there should be a "libp2p Bluetooth" specs, just like there's a "libp2p mDNS" specs for example. It should notably contain how devices discover each other (I went...
> So RFCOMM won't work for bluetooth on iOS Is it because iOS only gives you access to Bluetooth Low Energy? If so, as far as I know, streaming bytes...
This is low priority, as Substrate never uses this format. And it's something that has to be annotated manually, so Substrate won't magically start using it unless we decide so.