You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to security concerns (binary builds are a great hacking vector), loading AOT compiled binaries should be off-by-default.
As a configuration mechanism, employ a whitelisting mechanism that users can put in Scarb.toml:
Matching will happen on PackageName. Matching applies to the entire dependency subtree, that is, if package x is using macro y as its dependency, a whitelist entry x will allow package y. This means that a single whitelist item will enable all instances of a given macro, regardless of version/source differences. The transitive nature of the list also makes preserving some context within Scarb.toml file.
Example: usage by Starknet Foundry
Change snforge init template to emit a following Scarb.toml file for new projects:
Summary
Due to security concerns (binary builds are a great hacking vector), loading AOT compiled binaries should be off-by-default.
As a configuration mechanism, employ a whitelisting mechanism that users can put in
Scarb.toml
:Matching will happen on
PackageName
. Matching applies to the entire dependency subtree, that is, if packagex
is using macroy
as its dependency, a whitelist entryx
will allow packagey
. This means that a single whitelist item will enable all instances of a given macro, regardless of version/source differences. The transitive nature of the list also makes preserving some context withinScarb.toml
file.Example: usage by Starknet Foundry
Change
snforge init
template to emit a followingScarb.toml
file for new projects:Note
No such task was created in Foundry repo.
The text was updated successfully, but these errors were encountered: