Improve debugging by special debugging constructs / functions

[DanielMSchmidt]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Currently both finding the problem / potential errors and isolating error causes is a problem when debugging.
I would suggest us thinking in the direction of a Debugging Construct, e.g. that catches the error and prints it and increases the internal log levels of synth-time logs within its scope or functions that add meta-data to certain values that improve debugability, e.g. add context that a certain value is not expected to be a token, etc.

References

• The Rust web framework Axum uses a macro on handler functions called debug_handler to make errors thrown from the compiler in this section
• Rust has the concepts of marker traits. These are interfaces to implement on a custom type to indicate certain behaviour