In some cases, it is better to create an error message which explains to the user that a certain construct has not been implemented yet instead of panicking.
Summary
Show error message that a certain construct has not bee implemented as opposed to simply panicking.
Panicking should only occur in the case that an ASTNode is malformed, which should be caught in by the type checker. Perhaps it is best however to create a different error message for this instead of panicking.
Added Tests
Tests to check that an unimplemented error is thrown for the following constructs:
Relevant issues
94
In some cases, it is better to create an error message which explains to the user that a certain construct has not been implemented yet instead of panicking.
Summary
Show error message that a certain construct has not bee implemented as opposed to simply panicking. Panicking should only occur in the case that an ASTNode is malformed, which should be caught in by the type checker. Perhaps it is best however to create a different error message for this instead of panicking.
Added Tests
Tests to check that an unimplemented error is thrown for the following constructs: