Custom Query (1630 matches)
Results (7 - 9 of 1630)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1760 | invalid | IR-transformer not implicitly renaming? | ||
Description |
Is this by design or borked?
Prints "I said hey!" |
|||
#1761 | fixed | Port interface in z3 egg | ||
Description |
Decoding files work great, but on encoding: (display "Here is an example document to see if this thing can work "
Creates a pretty borked up file that can't be opened. |
|||
#1765 | worksforme | enable-warnings time-travelling shenanigans | ||
Description |
(import miscmacros (chicken condition)) (define-syntax-rule
(enable-warnings #f) (define wtf (bound-procedure? if)) (enable-warnings #t) wtf ;; ↑↑ quietly and politely evals to #f (begin
;; ↑↑ expands to a let form (which is fine of course) and complains in ;; the REPL because warnings apply retroactively to the entire form. I've tried enabling the warnings via (let ((ret ...)) enable ret) dynamic-wind or via force/delay or via just a lambda that gets called, but no matter how I do it, it retroactively wants to print warnings. I even did (define (re-enable-warnings val ret)
(re-enable-warnings #f (bound-procedure? if)) ;;; politely evals to #f (re-enable-warnings #t (bound-procedure? if)) ;;; causes a ruckus The time travelling super powers of call-with-current-continuation that the REPL uses is haunting me…! This just can't be right! |