Hello all,
Here's another patch set to improve support for source properties.
In brief:
* 'read' now sets source properties on non-immediate numbers: bignums,
floats, fractions, complex.
* add the 'supports-source-properties?' predicate (as well as
scm_supports_source_properties_p), which ca
Hi,
FWIW, I'm fine with whatever you all agree upon in the end, though I am
sympathetic to Mark's concerns here.
One thing:
On Tue 14 Feb 2012 17:56, Mark H Weaver writes:
> (compile x #:opts '(#:warnings (default no-format no-bad-case-datum)))
Let's pave this cowpath and add a #:warnings o
Hi Mark :)
On Tue 14 Feb 2012 19:57, Mark H Weaver writes:
> scheme@(guile-user)> my-filename
> $1 = #f
I get this result regardless of whether or not the (identity 1 2 3) is
there, at least with master; but perhaps that is to be expected, given
what you say:
> The same thing happens if I
On Wed 15 Feb 2012 18:50, Mark H Weaver writes:
> Here's another patch set to improve support for source properties.
LGTM in general. A few questions to address now or later; I'm fine with
pushing as is.
On the broad side, does the current "source-properties" mechanism make
sense? I get the f
Hello,
I've been working on a patch to add a new sort of optimization to
peval, and I think it's almost ready. It's based on some of the ideas
in "Environment Analysis of Higher-Order Languages".
The goal is to recognize when two quantities are equal even when we
don't know what they are. My work
Hi Noah,
Noah Lavine writes:
> I've been working on a patch to add a new sort of optimization to
> peval, and I think it's almost ready. It's based on some of the ideas
> in "Environment Analysis of Higher-Order Languages".
Nice! :)
> There's one glaring wart. The identity checking is activiate
Noah Lavine writes:
> Hello,
>
> I've been working on a patch to add a new sort of optimization to
> peval, and I think it's almost ready. It's based on some of the ideas
> in "Environment Analysis of Higher-Order Languages".
>
> The goal is to recognize when two quantities are equal even when we
David Kastrup writes:
> Noah Lavine writes:
>
>> Hello,
>>
>> I've been working on a patch to add a new sort of optimization to
>> peval, and I think it's almost ready. It's based on some of the ideas
>> in "Environment Analysis of Higher-Order Languages".
>>
>> The goal is to recognize when two