dominic

i saw the PR before i saw this. 1. sgtm as long as it's EOL 2. great! 3. i defer to your judgement.

i tried it on another rust project and it broke things, because rust projects don't stick to good semver and they break interfaces _all the time_. it's great for notifications...

having this as a cell, as a VM, as a CRI would be amazing. i don't know if mastodon is simple enough for an integration test, but as a proof...

we could fix the `PrintBasicContext` section to report on the number of CPUs _used_ if we got the current affinity somewhere i guess?

you're right that this isn't offered. the context here is that multi-threading something to benchmark it is anticipated to be to see what the impact of the threading (and thread...

by "auraescript" do you mean "a typescript API"? i wonder if we continue to support auraescript as a generated low-level typescript API but in addition we create a separate high...

there are two options for a typescript API i think: 1. auraed -> auto-generated auraescript -> hand-written typescript high-level API that offers an abstracted logic 2. auraed -> hand-written typescript...

thanks for the report. which compiler/OS are you on? and which version of benchmark are you building? the warnings/errors exist to provide information about possible mistakes, so removing it doesn't...

in this case, we're getting burned (finally) for using `offsetof` on a data structure that is very much not standard layout: it has non-static data members with different access control....

yes i'm not sure it's invalid either, but this at least unblocks us until this becomes an error. i'm open to hearing ideas for how to capture the spirit of...