When creating an executable distribution, the resulting zip file has no contents. I have updated to the most recent Racket release.
On Tue, Oct 19, 2021, 9:47 PM Hendrik Boom <hend...@topoi.pooq.com> wrote: > On Tue, Oct 19, 2021 at 11:07:58AM -0700, Sorawee Porncharoenwase wrote: > > On Tue, Oct 19, 2021 at 7:01 AM Diego Crespo > > mycontributiontothewo...@gmail.com > > <http://mailto:mycontributiontothewo...@gmail.com> wrote: > > > > If you are curious about what the output looked like before, here is the > > > pasterack link of some of my code http://pasterack.org/pastes/23639. > > > Racket supports using brackets instead of parenthesis, but you > typically > > > only see it used in things like cond and let expressions. This was > adding > > > them to far more expressions. Other than looking odd, there was nothing > > > wrong with the code (other than my own errors :)) > > > > > FWIW, here’s what the tool would output now (provided that the input > code’s > > paren shapes are not yet compromised): http://pasterack.org/pastes/21352 > > > > raco fmt will usually keep paren shape intact, but it can convert paren > > shape in some positions. Right now, the only conversion is from > parenthesis > > to bracket, and it’s enabled for: > > > > - cond, case-lambda, match, case body > > - syntax-case, syntax-rules body > > - syntax-parse (including syntax-parser and define-syntax-parser) > body. > > - for bindings (including for/... and for*/...) > > - let bindings (including letrec, let-syntax, let-values, …) > > - parameterize, with-syntax, shared bindings > > - and a few more > > > > What happened earlier was that class was erroneously configured to have > > this paren shape conversion, even though it should not. > > I find the layout of the second version more readable, > but find the choice of parenthesis shape in the first version more > readable. > > -- hendrik > > > > > On Tuesday, October 19, 2021 at 9:34:04 AM UTC-4 hen...@topoi.pooq.com > > > wrote: > > > > > >> and was disappointed. > > >> > > > I would not recommend this, but if you strongly feel that the class > body > > should use brackets, you are free to write your own formatting rules. > > (Though I have not documented how to do so.) > > > > -- > > You received this message because you are subscribed to the Google > Groups "Racket Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to racket-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-users/CADcuegs%2BepCLAXHzjXxPdq%3DR6su0heHOJRBYgWL7_tLj5J%3Db2A%40mail.gmail.com > . > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/racket-users/20211020014753.yl36iozz5wzpcyzb%40topoi.pooq.com > . > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CALu3OuiJ2-_GgAynYFxyoUwWAjs08giUJxT_gBSqRexTYz-Jnw%40mail.gmail.com.
