Post B2aCk1tORjYAg9vAJs by wim_v12e@merveilles.town
 (DIR) More posts by wim_v12e@merveilles.town
 (DIR) Post #B2a7IrPUoMqOZzA7W4 by neauoire@merveilles.town
       2026-01-23T16:08:14Z
       
       0 likes, 0 repeats
       
       @wim_v12e this is real nice, the warnings are great. I was wondering if you knew about these assemblers tests, they might come in handy:https://git.sr.ht/~rabbits/drifblim/tree/main/item/tests.shhttps://git.sr.ht/~rabbits/drifblim/tree/main/item/etc/tests/acid.tal
       
 (DIR) Post #B2aCQXmYAiItn7QdwO by wim_v12e@merveilles.town
       2026-01-23T17:05:47Z
       
       0 likes, 0 repeats
       
       @neauoire Thanks, I had looked at tests.sh but not at acid.tal. Will check it out.The warnings are overly strict, but it is based on all the mistakes I observed my students making. Will be nice to see if it helps this year's cohort.
       
 (DIR) Post #B2aCZzYeGtNIXhQod6 by neauoire@merveilles.town
       2026-01-23T17:07:37Z
       
       0 likes, 0 repeats
       
       @wim_v12e The "canonical" way for uxn tools like uxnlin to mute warnings is to wrap inside of square brackets, that might be a good way for this as well? [ LIT2 "0 -Console/write DEO ]     ( Print failure )
       
 (DIR) Post #B2aCk1tORjYAg9vAJs by wim_v12e@merveilles.town
       2026-01-23T17:09:27Z
       
       0 likes, 0 repeats
       
       @neauoire That is a good idea. Currently I simply ignore the square brackets, adding a little state to suppress warnings shouldn't be too hard. I just need to create a token for them.