Alec Theriault
Alec Theriault
This is more of a question that an issue. One of the most common requests for Haddock is to support markdown. This has somewhat controversial - everyone agrees Haddock is...
One way to do this is by calling `cargo rustc -- --print=native-static-libs` from the directory containing the `Cargo.toml`. It would be nice to parse this and print out a more...
There is some trickiness around `FunPtr` and `"dynamic"` foreign imports. See the docs on [`FunPtr`](https://hackage.haskell.org/package/base-4.10.0.0/docs/Foreign-Ptr.html#g:2) for more information.
Consider ```haskell newtype Box t = Box { unBox :: ForeignPtr t } ``` It might be interesting to match `Box` types to `Box t`. The useful part would be...
Right now, it is expected that `rustc` be on PATH. That shouldn't be the case. Also, we ought to be able to pass in more `rustc` options.
In the course of writing a test suite, I ran into the following issue: there is no good way of linking in 2 different rust-produced artifacts in different modules without...
I think we will want: | Haskell | Rust argument | Status | | ------------- |-------------|----| | `StorableArray Int a` | `&mut [a']` | see https://github.com/harpocrates/inline-rust/issues/12 | | `Vector a`...
References at the top level should be possible. For example: ``` main = do let s: S = {- some complex deeply nested struct (but not enum!) -} [rustIO| ()...
I expect it will very quickly become frustrating to have a `Could not find information...` error message. We should accumulate some information about failed context matches in a `Writer` and...
Both when creating contexts and when looking up Rust types from Haskell types, we should expand out Haskell type synonyms. The arguments against doing this are: * we have to...