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
{{ message }}
This repository has been archived by the owner on Jan 7, 2022. It is now read-only.
We should almost certainly follow RPython's lead and make functions do_not_trace by default if they contain a loop so that we don't unroll arbitrary loops. For example if someone has a function like this:
fnf(){for _ in0..100000{ ...}}
we don't want to trace the whole function! Rather we want that to be equivalent to:
#[do_not_trace]fnf(){for _ in0..100000{ ...}}
At some point we'll probably want to introduce an RPython-esque unroll_safe annotation that allows one to override this default.
The text was updated successfully, but these errors were encountered:
We should almost certainly follow RPython's lead and make functions
do_not_trace
by default if they contain a loop so that we don't unroll arbitrary loops. For example if someone has a function like this:we don't want to trace the whole function! Rather we want that to be equivalent to:
At some point we'll probably want to introduce an RPython-esque
unroll_safe
annotation that allows one to override this default.The text was updated successfully, but these errors were encountered: