Skip to content

Conversation

@cgay
Copy link
Member

@cgay cgay commented Mar 25, 2025

There is still one call to debug-message("Hello") but I don't know if capturing its output is doable.

There is still one call to debug-message("Hello") but I don't know if capturing its
output is doable.
@cgay cgay requested a review from fraya March 25, 2025 14:36
@cgay cgay merged commit 3f9beee into dylan-lang:master Mar 27, 2025
2 of 3 checks passed


define constant *print-lock* = make(<lock>);
define constant $debug-threads-tests = #f;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand why this is used. Is a constant and is not used in another place, so is like the block below is not gonna be executed. I could understand if is a define thread variable. Can you explain me why?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It could be a variable instead. It's just that I found it hard to imagine someone entering the interactor/debugger, setting the variable, and then running the tests.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it really just provides a way to make a one-letter change (f -> t) to see the output if desired. It would've been fine to just delete the output code entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants