Wow. In addition to getting my question answered, I learned about 6 other
things. Thank you so much, everyone!
Glenn
--
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 ema
Everyone:
this discussion is the first time that we have a rough tone on this mailing
list,
and this tone is inappropriate.
I am appealing to both sides to cool it down.
We (the organizers and old people of this community) appreciate all
non-emotional
input. Science and science organizati
Here's another:
(define/contract (ucfirst str)
(-> string? string?)
(match (regexp-match #px"^([^a-z]*)(.)(.+)" str)
[(list _ prefix first-letter rest-of-string)
(~a prefix (string-upcase first-letter) rest-of-string)]))
-> (ucfirst "cat dog")
"Cat dog"
-> (ucfirst " Cat dog")
" Ca
On 06/17/2017 01:50 PM, Matthias Felleisen wrote:
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.
I think you might be reading something in to this r
I think this thread has gotten delightfully meta, in that I've heard
that some people who would like to contribute in forums get scared away
when observing interaction styles that they find very confrontational.
Not that I always remember this myself, and I also make other mistakes,
but... Whe
Robby's answer was more idiomatic Racket, and mine was
idomatic-Scheme-and-also-OK-Racket, by habit. :)
I'd suggest reading both implementations. As you learn more Racket,
you'll start to get a feel for your preferred linguistic style(s), and
you'll notice different people have a lot more sty
If by whiskey, Jack. Your guarantees on this matter are unenforceable and
therefore meaningless, and any further comment on my ignorance will likely
violate any CoC you care to throw your weight behind, so best get it out
now because you can't unring this bell.
On Mon, Jun 19, 2017 at 8:08 PM, Jac
On Mon, Jun 19, 2017 at 8:12 PM, Glenn Hoetker wrote:
> I'm quite new to Racket/LISP, so I hope this isn't breathtakingly obvious.
> Can someone please tell me the best way to capitalize just the first word in
> a multiword string. So, given the string "it was a dark and stormy night", I
> wo
Given how many solutions everyone's giving, this would be a good rosetta code
task :)
--
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...@g
Here's another way to implement it. Fun. :)
#lang racket
(provide
(contract-out
[cap-first (-> string? string?)]))
(define (cap-first s)
(apply
string
(for/list ([c (in-string s)]
[i (in-naturals)])
(if (= i 0)
(char-upcase c)
c
(module+ test
Welcome to Racket!
One intro-to-Racket-compared-to-some-other-languages thing I'll just say
upfront is that you don't want to modify the string itself, not that you
asked to. (Not all Racket strings are mutable. Plus, mutating
introduces a bunch more possibilities for bugs, and for string
o
On Monday, June 19, 2017 at 5:12:10 PM UTC-7, Glenn Hoetker wrote:
> I'm quite new to Racket/LISP, so I hope this isn't breathtakingly obvious.
> Can someone please tell me the best way to capitalize just the first word in
> a multiword string. So, given the string "it was a dark and stormy nig
I don't think there's a library function that does what you want, so you'd
need to define your own. Here's one way to do it:
(define (capitalize-first-letter str)
(cond
[(non-empty-string? str)
(define first-letter-str
(substring str 0 1))
(define rest-str
(substring
I'm quite new to Racket/LISP, so I hope this isn't breathtakingly obvious. Can
someone please tell me the best way to capitalize just the first word in a
multiword string. So, given the string "it was a dark and stormy night", I
would like to get "It was a dark and stormy night". I see functio
> These are invariably motte and bailey style arguments and the notion that the
> only reason I or anyone else could possibly resent CoCs is some desire to
> abuse their absence is astonishing. How you could not find such groupthink
> "censorious" is beyond my ability to sympathize with. I can o
This is not my call, but in the traditional Racket convention of
everyone voicing thoughts...
One gentle way to communicate awareness and intent of inclusiveness:
"The Racket community enjoys and appreciates a collegial and
helpful atmosphere, in which everyone feels welcome. We expect th
>Bluntly, if someone finds the admonition to refrain from harassment
"censorious", then it is likely they are exactly the sort of person that a
Code of Conduct is in fact *designed* to make feel unwelcome.
These are invariably motte and bailey style arguments and the notion that
the only reason I
>
> The problem with the longer text, such as the Strange Loop one[1], is that
> it's manifestly _very_ hard to come up with a text that doesn't radiate
> censoriousness; and however much this isn't the literal implication of the
> text, it does implant the notion that the reader or the community h
I would suggest that it is more important to get a COC on the RacketCon
website than it is to argue over the wording. I would suggest that every
day that passes without a CoC on the website adds to the risk that possible
racketcon participants might decide not to go... to the detriment of the
Racke
Greetings.
On 19 Jun 2017, at 16:18, John Berry wrote:
Nothing about a document saying "hey, don't be an ass" implies that
the
reader themselves, or the community, are asses. Only that the
community
values not being an ass, and those who might wish to join that
community
and not be an ass ar
I will always 100% support the adoption of a CoC drafted by people with
experience in dealing with discrimination, harassment, and toxic behaviour.
It is impossible to understate just how much gets swept under the rug
without one, and increasingly, the lack of one itself tends to attract
toxic peop
Strange Loop one looks good.
--
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.
For more options, visit https://groups.go
22 matches
Mail list logo