Skip to content

Working on the standard library in VScode #2730

@jurgenvinju

Description

@jurgenvinju

I would like a special mode, or configuration option in VScode for
working on the standard library.

Currently the rascal project is configured for working on the compiler or the tutor, since you always
need a stable, previously released, stdlib for that. The standard lib is not on the source path and the
other code is.

A "reversed" mode where the other code is not on the source path but the standard library is can
only work if the builtins in Java are not changed. If you do want to edit library code that changes builtins, you should start your own RascalShell in debug mode and work with that.

But for the formatter and parser generator and other larger projects hidden in the stdlib it would be nice to have a:

  • terminal REPL with the correct source path
  • type-checker configured correctly
  • working interactive debugger.
  • nice warnings/errors if you accidentally modify a builtin.

@rodinaarssen do you have thoughts on this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions