These pragmas are part of the VM's API and are safe for use in external code.
|Defining entry-points into Dart code for an embedder or native methods
|Never inline a function or method
|Inline a function or method when possible
|Marks a function that catches exceptions, making the VM treat any caught exception as if they were uncaught. This can be used to notify an attached debugger during debugging, without pausing the app during regular execution.
These pragmas are available for use in third-party code but are potentially unsafe. The use of these pragmas is discouraged unless the developer fully understands potential repercussions.
CheckStackOverflow instructions from the optimized version of the marked function, which disables stack overflow checking and interruption within that function. This pragma exists mainly for performance evaluation and should not be used in a general-purpose code, because VM relies on these checks for OOB message delivery and GC scheduling.
These pragmas can cause unsound behavior if used incorrectly and therefore are only allowed within the core SDK libraries.
|Declaring an exact result type of a method
|Marking this as a recognized method
These pragmas are used for inspecting or modifying internal VM state and should be used exclusively by SDK tests. They must be enabled with the
--enable-testing-pragmas flag. The names of these pragmas are prefixed with “testing”. Additionally, they are categorized into “safe” and “unsafe” forms: “safe” pragmas should not affect the behavior of the program and can be safely added anywhere, whereas “unsafe” pragmas may change the code's behavior or may cause the VM to crash if used improperly.
|Observing which flow-graph-level entry-point was used when a function was called