As a `require` form, a `submod`'s binding context is taken from the
parenthesis around the `submod`. With options (A) and (B), the context
of those parentheses is macro-introduced.
At Sat, 17 Jun 2017 16:49:50 -0400, Tony Garnock-Jones wrote:
> #lang racket
> ;;
> ;; Hi all (Matthew in particular
I don't believe virtue signaling can ever substitute for actual virtue. If,
however, a failure to signal virtue is interpreted as a vice, then this is
a sticky situation indeed. There is the argument that if everyone behaved
we wouldn't need laws, but there is also the argument that people still
Unfortunately, event "codes of conduct" started, in part, as reactions
to actual bad behavior at some (non-Racket) events.
I agree that RacketCon doesn't need a code of conduct to tell people how
to behave. But people relatively new to Racket might not know that.
Hence, the conventional
+1 for a code of conduct from me.
Although I can only rarely attend RacketCon (coming from Australia) codes
of conduct seem to have had a net positive effect at local conferences:
enhancing inclusivity and tone.
Perhaps one day such codes can be optimized away, but in the present day
requiring
#lang racket
;;
;; Hi all (Matthew in particular I imagine :-) ),
;;
;; Why does option (C) work, but options (A) and (B) do not?
;;
;; They fail with:
;;
;; t.rkt:31:2: v1: unbound identifier in module
;; in: v1
;; context...:
;;standard-module-name-resolver
;;
;; -- Tony
(require
A code of conduct is a totally stupid idea for RacketCon. Racketeers were
raised properly by their parents and are well behaved. I really hate attending
conferences that need to impose a code.
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
6 matches
Mail list logo
