More robust in-Ludus testing #21
Labels
No Label
accepted
bug
clj
documentation
enhancement
errors
infrastructure
later
next
now
optimization
proposal
question
research
semantics
syntax
ux
vm
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: twc/ludus#21
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We've got
test
expressions in #8. That's swell!One issue is that there's no way to test when something should panic. Right now, tests pass only when there's no panic. How do we get a positive result when there's a panic, since there's now way to trap a panic in Ludus? (By design!) Maybe this is just a limitation of the language.
For consideration.