Comments on draft #3
Marc Nieper-Wißkirchen
(26 Apr 2020 10:22 UTC)
|
||
(missing)
|
||
Re: Comments on draft #3
Marc Nieper-Wißkirchen
(27 Apr 2020 05:50 UTC)
|
||
Re: Comments on draft #3 Marc Nieper-Wißkirchen (02 May 2020 21:08 UTC)
|
||
Re: Comments on draft #3
John Cowan
(02 May 2020 22:11 UTC)
|
||
Re: Comments on draft #3
Marc Nieper-Wißkirchen
(03 May 2020 09:06 UTC)
|
||
Re: Comments on draft #3
Marc Nieper-Wißkirchen
(03 May 2020 15:51 UTC)
|
||
Re: Comments on draft #3
Marc Nieper-Wißkirchen
(03 May 2020 16:10 UTC)
|
||
Re: Comments on draft #3
Marc Nieper-Wißkirchen
(05 Jun 2020 06:19 UTC)
|
||
Re: Comments on draft #3
Marc Nieper-Wißkirchen
(03 May 2020 13:56 UTC)
|
||
Re: Comments on draft #3
Marc Nieper-Wißkirchen
(03 May 2020 14:03 UTC)
|
||
Re: Comments on draft #3
John Cowan
(02 May 2020 22:56 UTC)
|
||
Re: Comments on draft #3
Marc Nieper-Wißkirchen
(04 May 2020 09:34 UTC)
|
||
Re: Comments on draft #3
John Cowan
(05 May 2020 01:05 UTC)
|
||
Re: Comments on draft #3
Marc Nieper-Wißkirchen
(05 May 2020 07:11 UTC)
|
Am Mo., 27. Apr. 2020 um 07:50 Uhr schrieb Marc Nieper-Wißkirchen <xxxxxx@nieper-wisskirchen.de>: [...] > Could you explain in more detail what efficiency problems you see with > defaults and why they couldn't be handled by the implementation? Did you get this message? I am really interested to know why you think defaults can have efficiency issues. What I can deliver is a macro, say DEFINE*, through which one can define a procedure taking optional arguments and optional keyword arguments (after all optionals are given), which has no runtime overhead compared to a procedure taking no optional arguments and no optional keyword arguments as long as keywords are given in the form 'keyword. The macro will have to depend on identifier macros (otherwise we wouldn't be able to pass around the defined "procedure"). However, identifier macros should be almost trivial to implement in any Scheme expander, while it is much harder to implement an optimizer that can optimize such calls.