Skip to content

Should be able to control how the compiler responds to uncompilable code. #289

@braxtonmckee

Description

@braxtonmckee
Collaborator

Right now, we attempt to compile everything. If we see something we don't understand in the compiler, we attempt to convert everything to 'object' and call the interpreter. This is preferable if you want everything to work, but it can make it difficult to detect when your code is slow because you are doing something typed_python doesn't know how to compile.

To alleviate this, we should add something to Runtime to let us decide how the compiler responds to things it can't compile, letting us choose between compiling it to the interpreter silently, compiling it but logging it as a warning, or refusing to compile it and throwing a compile-time error.

Activity

added
compilerIssue that does not affect the un-compiled subset of typed_python
on Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    compilerIssue that does not affect the un-compiled subset of typed_pythonfeature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @braxtonmckee

        Issue actions

          Should be able to control how the compiler responds to uncompilable code. · Issue #289 · APrioriInvestments/typed_python