Allow isolates to be spawned with separate environment constants #23799
Labels
area-core-library
SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries.
library-isolate
type-enhancement
A request for a change that isn't a bug
type-security
When spawning an isolate, it would be useful to control what environment constants are available within that isolate. This would be nice for things like
pub run
or thetest
package runner, where the user may specify environment constants on the command line. It can also be looked at as a security feature; if an isolate is used to run untrusted code, the caller may not want the isolate to have access to its environment constants, which may contain secret information.The text was updated successfully, but these errors were encountered: