unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: my latest blog post
Date: Fri, 8 Jun 2018 09:39:21 +0000	[thread overview]
Message-ID: <20180608093921.fyj3czzlcfdzoov5@abyayala> (raw)
In-Reply-To: <CAJ98PDzdEVBqBuz5DiVQT1LTbzmRoQ4MACjTPzu5Jr3DvWJftg@mail.gmail.com>

Catonano transcribed 7.7K bytes:
> Mark,
> 
> 2018-06-07 19:03 GMT+02:00 Mark H Weaver <mhw@netris.org>:
> 
> I appreciate you sharing your thoughts on this.  I wanted to apologize
> > for making you feel badly; it honestly was not my intent to shame you in
> > any way.
> >
> 
> Thank you for your kind and measured words
> I appreciate both the tone and the content of your reply
> 
> I am very reassured by your statement that you find my quuestions about
> macro expansion reasonable and legitimate
> 
> My feeling was not positive and I'm only happy of having been wrong
> 
> 
> > To be honest, I felt a bit defensive when you seemed to contradict my
> > claim that 'macroexpand-1' would be difficult to implement in a modern
> > Hygienic macro expander, when you pointed to the Racket documentation
> > and asked (possibly rhetorically) whether Racket had hygienic macros.
> > What felt to you like "slight shaming" might have been somehow related
> > to my feeling defensive about this.
> >
> 
> I see
> 
> On my side, I was a bit adversary because I feel that a macro stepper is a
> fundamental feature of a scheme system and in Guile it's less than an
> afterthought
> 
> I understand that implementing it is too much work
> 
> But I think that the manual should at least mention macro stepping as a
> missing feature, it should mention the internal APIs that you indicated in
> that thread and the uncertainties around them
> 
> What I want to convey is that the user shouldn't be left in the dark about
> macro stepping
> 
> On the bright side, after this discussion, I offer to contribute a
> paragraph for the manual where the macro stepping missing feature is
> discussed
> 
> It will still be a missing feature, but at least the user will know what
> she needs to know
> 
> I'd use the enlightening example you provided, the warings you raised and
> the notions contained in the paragraph about the syntax helpers
> 
> Probably the part that's not about syntax helpers should be pulled out from
> there and integrated in the new paragraph

Just my brief encouragement:

I'm not sure how active the Guile documentation writer(s) are, but if you
know how to write it or initially draft something that would be great.
Writing the code is good, but documenting it affects much more people and
would be a good outcome of the discussion :)

> > My lack of response until now to your most recent message in that thread
> > was not because my "patience was exhausted", as you wrote, but only
> > because I'm stretched far too thin, and I haven't yet figured out how to
> > respond to your last message.
> >
> > I simply don't have enough time for all of the things I'd like to do, so
> > many important things get dropped on the floor.  I respond to user
> > questions and bug reports sporadically, when I have the time and energy
> > to do so.  It's nothing personal.
> >
> 
> I'm so relieved in learning you didn´t shrug it
> 
> Someone else made me notice that the lack of an answer can't always be
> interpeted as an aggression, as I did in my post.
> 
> I did, indeed.
> 
> The lack of an answer hits me, admittedly
> 
> I apologize for being emotional about this
> 
> 
> >
> > For what it's worth, I think that your line of questions about
> > 'macroexpand-1' was perfectly reasonable, and neither worthy of shame
> > nor of feeling like an idiot.  The details of modern macro expanders are
> > quite difficult, and I suspect that even seasoned Scheme hackers rarely
> > understand them in depth.
> >
> >      Regards,
> >        Mark
> >
> 
> 
> thanks

  reply	other threads:[~2018-06-08  9:38 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 15:25 my latest blog post Catonano
2018-06-07 16:28 ` Joshua Branson
2018-06-08  4:24   ` Christopher Lemmer Webber
2018-06-08  6:18     ` Fis Trivial
2018-06-08 14:02       ` Ricardo Wurmus
2018-06-08  8:25     ` Catonano
2018-06-08 13:51       ` Fis Trivial
2018-06-08 14:25       ` Ricardo Wurmus
2018-06-09  7:47         ` Catonano
2018-06-09 12:24           ` Ricardo Wurmus
2018-06-09 13:07             ` Catonano
2018-06-09 15:29               ` Christopher Lemmer Webber
2018-06-09 13:51             ` Christopher Lemmer Webber
2018-06-07 17:03 ` Mark H Weaver
2018-06-07 19:40   ` Catonano
2018-06-08  9:39     ` Nils Gillmann [this message]
2018-06-08  9:45       ` Catonano
2018-06-08 18:05     ` Mark H Weaver
2018-06-09  7:00       ` Catonano
2018-06-09 10:39         ` Ricardo Wurmus
2018-06-09 10:52           ` Catonano
2018-06-09 12:14             ` Ricardo Wurmus
2018-06-09 13:03               ` Catonano
2018-06-10 10:53         ` Mark H Weaver
2018-06-07 18:11 ` Thorsten Wilms
2018-06-07 21:45 ` Alex Vong
2018-06-08  9:15 ` Julien Lepiller
2018-06-08  9:34   ` Clément Lassieur
2018-06-08  9:45     ` Julien Lepiller
2018-06-08 13:50   ` Widen info Oleg Pykhalov
2018-06-08 13:59     ` Julien Lepiller
2018-06-08 13:49 ` my latest blog post Ludovic Courtès
2018-06-09  5:59   ` Catonano
2018-06-09 22:49 ` myglc2
2018-06-10  0:51   ` Mark H Weaver
2018-06-10  6:55     ` Pjotr Prins
2018-06-10  9:07       ` Catonano
2018-06-10  9:29         ` Ricardo Wurmus
2018-06-10  9:30           ` Catonano
2018-06-10 10:37             ` Ricardo Wurmus
2018-06-10 10:45         ` Mark H Weaver
2018-06-10 12:06         ` Pjotr Prins
2018-06-10  7:58     ` Catonano
2018-06-10  9:26       ` Ricardo Wurmus
2018-06-10  9:27         ` Catonano
2018-06-10 19:13           ` Ludovic Courtès
2018-06-10  8:07   ` Catonano
2018-06-10 19:23     ` Ludovic Courtès
2018-06-10  8:17 ` my latest blog post [everyone, please take a cooldown break] Nils Gillmann
2018-06-10 13:33   ` Christopher Lemmer Webber
2018-06-10 14:18     ` Gábor Boskovits
2018-06-10 14:37       ` Kei Kebreau
2018-06-11  6:01         ` swedebugia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180608093921.fyj3czzlcfdzoov5@abyayala \
    --to=ng0@n0.is \
    --cc=catonano@gmail.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).