> On Fri, Jun 3, 2022 at 7:21 AM David Kastrup wrote:
> Programming languages don't offer different types for distances,
> positions, weights, forces, whatnot.
It's safe to say that programming languages don't typically don't offer
much in the way of types, they do however usually allow you to
Here is the current countdown list.
The next countdown will be on June 5th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
No patches in Push at this time.
Countdown:
!1396 Stop using global header
Jean Abou Samra writes:
> Nice! I wasn't aware that GOOPS had become faster
> in Guile 2, nor even that it supported smob types.
> I had stayed in the conception that it was a "don't
> use" module.
I am not sure how much this may have changed. One would certainly need
to check how much it
Jean Abou Samra writes:
> Le 03/06/2022 à 02:32, David Kastrup a écrit :
>> GOOPS was supposed to cause quite a performance hit with Guile 1.8 when
>> used extensively. It wasn't supposed to do this with Guile 2+ so
>> something like this should be feasible, also for other types:
>>
>>
Le 03/06/2022 à 02:32, David Kastrup a écrit :
GOOPS was supposed to cause quite a performance hit with Guile 1.8 when
used extensively. It wasn't supposed to do this with Guile 2+ so
something like this should be feasible, also for other types:
#(use-modules (oop goops))
#(define (class-of
Dan Eble writes:
> On Jun 3, 2022, at 11:48, David Kastrup wrote:
>>
>> Programming languages don't offer different types for distances,
>> positions, weights, forces, whatnot. When I equate various amounts of
>
> Bringing the conversation back to a Moment versus the delta between
> two
Dan Eble writes:
> At a minimum, we could forego defining (+ Moment Moment) -- or is
> there a need to expand the loose dealings of the past into a new area?
We don't have a separate data type for time lengths, and I don't really
see an expected gain for such a one.
> Maybe we could globally
On Jun 3, 2022, at 11:48, David Kastrup wrote:
>
> Programming languages don't offer different types for distances,
> positions, weights, forces, whatnot. When I equate various amounts of
Bringing the conversation back to a Moment versus the delta between two
Moments, C++11 has
On 2022-06-03 8:48 am, David Kastrup wrote:
Frankly, that's academic. It reminds me of the excessive amount of
energy placed into keeping the mathematics(!) of location vectors and
difference vectors separate.
Homogenous coordinates: "When in doubt, define a new dimension." :)
-- Aaron
Carl Sorensen writes:
> On Fri, Jun 3, 2022 at 7:21 AM David Kastrup wrote:
>
>> Dan Eble writes:
>>
>> > On Jun 2, 2022, at 20:32, David Kastrup wrote:
>> >>
>> >> #(define-method (+ (a ) (b )) (ly:moment-add a b))
>> >> #(define-method (- (a ) (b )) (ly:moment-sub a b))
>> >
>> > Could we
On Fri, Jun 3, 2022 at 7:21 AM David Kastrup wrote:
> Dan Eble writes:
>
> > On Jun 2, 2022, at 20:32, David Kastrup wrote:
> >>
> >> #(define-method (+ (a ) (b )) (ly:moment-add a b))
> >> #(define-method (- (a ) (b )) (ly:moment-sub a b))
> >
> > Could we also introduce a distinction in type
Dan Eble writes:
> On Jun 2, 2022, at 20:32, David Kastrup wrote:
>>
>> #(define-method (+ (a ) (b )) (ly:moment-add a b))
>> #(define-method (- (a ) (b )) (ly:moment-sub a b))
>
> Could we also introduce a distinction in type between points and spans
> of time? "Measure 12 minus Measure 8"
On Jun 2, 2022, at 20:32, David Kastrup wrote:
>
> #(define-method (+ (a ) (b )) (ly:moment-add a b))
> #(define-method (- (a ) (b )) (ly:moment-sub a b))
Could we also introduce a distinction in type between points and spans of time?
"Measure 12 minus Measure 8" is 4 measures, but it is not
13 matches
Mail list logo
