> In the same way that properties can now be attached as preserved or
> not, we could and an option for specifying whether properties are are
> propagated/merged or not. If it's useful, we could even allow a
> combining function to be associated with with either a property value
> or a property
On Thu, 21 Apr 2016 15:55:34 -0500,
Matthew Flatt wrote:
> In the same way that properties can now be attached as preserved or
> not, we could and an option for specifying whether properties are are
> propagated/merged or not. If it's useful, we could even allow a
> combining function to be
At Thu, 21 Apr 2016 11:45:08 -0700 (PDT), Jack Firth wrote:
> The documentation for syntax properties states that if a macro sets a syntax
> property during expansion then instead of the expanded syntax having only the
> set value, it has a cons tree containing that value and any previous values
The documentation for syntax properties states that if a macro sets a syntax
property during expansion then instead of the expanded syntax having only the
set value, it has a cons tree containing that value and any previous values set
for that same property. As I understand it, this means it's
4 matches
Mail list logo
