Skip to content

Unsafe optimizations #4

Description

@redknightlois

The implementation of unsafe optimization implies accessing fields on first use, create the local variables and let the optimization method to do its work.

Allowing the use of fields while unsafe in the general case (because of multithreading) should be allowed via the use of an attribute.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions