They probably all produce the same bitcode in the part that we care about, so this is getting too complicated. IMO the wasm32 output should be generic enough for our purposes. Can inkwell load it…
I will look into how to delete all these function attributes in inkwell.
That doesn't sound very nice... Are you sure there isn't a way to make Clang output generic LLVM bitcode?
…
and what package management mess will there be if using parse from path?
If nac3artiq.so depends on some external files:
- they need to be copied along with it in an appropriate…
This will break with packaging and create a mess that nobody wants to solve. I had told you several times to use include_bytes! and Module.parse_bitcode_from_buffer.
Oh ok I will use…
I end up still using c to implement the slice assignment function. Because if I did not miss something, we need VLA or explicit stack alloca for list assignment, and in rust, these two features are…
df5eee9ae3
nac3core: make list slice index inclusive internally to handle cases when end index is None
61d89cd16c
nac3core: make list slice index inclusive internally to handle cases when end index is None
e10ed55914
nac3core: make list slice index inclusive internally to handle cases when end index is None
We may need to document that we do not support a[:None:-1] (maybe we can after implementing the Option type?), which is equivalent to a[::-1], which is NOT equivalent to a[:0:-1] since the…
