Opened 13 years ago
Closed 13 years ago
#797 closed defect (worksforme)
eggs that are misusing the assert macro
| Reported by: | Christian Kellermann | Owned by: | juergen |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | extensions | Version: | 4.7.x |
| Keywords: | assert eggs macro | Cc: | Alaric Snell-Pym |
| Estimated difficulty: |
Description
Recent changes enforce the msg argument of assert to be a string. This triggers an error in
- er-macros
- contracts
- tubles
- skiplists
- ugarit
For details see for example this salmonella report:
http://tests.call-cc.org/master/linux/x86/2012/03/07/salmonella-report/
I am attaching this to juergen since most of this are his, alaric in CC for ugarit...
Change History (3)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
| Milestone: | 4.8.0 |
|---|
comment:3 Changed 13 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Is it a misuse of assert to have an expression that generates a string as the message? I'd argue that this is a useful feature, to dynamically generate more informative assertion failure messages :-)
I have submitted a patch to chicken-hackers that would re-enable this; let's see if consensus is that assert needs to have a static string argument!