Nick Fitzgerald
Nick Fitzgerald
> How would this work? Even with an implementation that has a feature flag (which not all will have), how does it recognise the outdated tests when the flag is...
Interesting... It's really only the last one? That is annoying because it means we can't always inline, which would be easier (if we have to do any inlining at all)....
That makes much more sense to me.
And means that the always-inline-base-members-and-generate-upcast-methods approach is more reasonable, no?
Nice! Will take a look later today!
I haven't used lists in smt-lib2 very much, but the answer is that it works the same in this crate as however it does in smt-lib2. You should be able...
> This is useful when embedder uses multiple `Engine` objects with different config. If the engines have different configs, then the same compiled artifact will not be compatible with all...
(And if the engines all have the same config, then you might as well just use one engine.)
> the ability to say "give me a module based on this (to me) opaque identifier." That's what the preopen API that Alex sketched is for. FWIW I would bikeshed...
Also, listing all pre-compiled modules might not be something we want to expose, since the pre-compiled modules could come from the network in a FaaS platform, and then we would...