…context in transpiler

Proposed changes

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes an bug or resolves a feature request, be sure to link to that issue.

Types of changes

What types of changes does your code introduce to Bitloops Language?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the Bitloops Language CLA (if not, email us: [email protected])
• I created tests which fail with the change
• Code complies correctly
• Unit tests pass locally with my changes
• All existing tests passed
• I have added tests that prove my fix is effective or that my feature works
• I have added/extended necessary documentation
• Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...