<sobel>
ugh. and Guest66 should stick around longer than an hour.
fling_ has joined #openscad
fling has quit [Ping timeout: 260 seconds]
<J24k54>
I like to work for your company .. btw. can you tell me what your company does?
fling_ is now known as fling
<gbruno>
[github] lgarron opened issue #5437 (SIGSEGV when using `minkowski(&)` with Manifold, different behaviour depending on how OpenSCAD was invoked.) https://github.com/openscad/openscad/issues/5437
<gbruno>
[github] lgarron opened issue #5438 (App crashes with SIGSEGV when using `minkowski(&)` with Manifold, different behaviour depending on how OpenSCAD was invoked) https://github.com/openscad/openscad/issues/5438
<gbruno>
[github] lgarron edited issue #5438 (App crashes with SIGSEGV when using `minkowski(&)` with Manifold, different behaviour depending on how OpenSCAD was invoked) https://github.com/openscad/openscad/issues/5438
<sobel>
J24k54: ikr!?
mmu_man has joined #openscad
<gbruno>
[github] lgarron edited issue #5438 (App crashes with SIGSEGV when using `minkowski(&)` with Manifold, different behaviour depending on how OpenSCAD was invoked) https://github.com/openscad/openscad/issues/5438
<InPhase>
Function f is defined once per recursion, so comparing f from one entry into test, to f from the second entry into f, compares not equal. This is, I feel, the correct behavior, because they are in different contexts. But it could catch one by surprise.
<InPhase>
Functions can obtain values and behaviors that differ due to the values within their contexts, so it should in fact do this.
<InPhase>
So the answer to your question is still "yes", if you sufficiently understand what "itself" means. :)
<InPhase>
Only true if the same function assignment evaluated as a function literal within the same context.
<invultri>
Which is enough, I just wanted something to distinguish 'unset' from undef or nan
<InPhase>
invultri: Uhm, doesn't that call all parameter levels of that function, and only keep one result?
<InPhase>
Oh, nevermind.
<InPhase>
No, you're fine.
<InPhase>
Be advised that trailing list comma after map is a nightly build feature not yet present in the last stable release.
<InPhase>
It was added to increase syntax tolerance, but a side effect is some people developing with nightly accidentally leave them in when they didn't mean to. :)
<invultri>
you mean [a,b*,*] ?
<InPhase>
let(a=5, b=6,)
<InPhase>
The last comma
<InPhase>
Or in your case, [a,b,]
<invultri>
ah, well I think I am stuck to nightly anyway (and yes, those ** was to highlight but my irssi is rather old)
<InPhase>
Ah, one of those was already supported in the last release. I just tested. Only the let one trips it up on yours.
<InPhase>
Only a concern if you share and expect it to work in stable.
mmu_man has quit [Ping timeout: 272 seconds]
<invultri>
Pretty sure no-one is waiting for this :) if I figured out what is wrong I will post the result
<invultri>
I think I will stick to this over currying. Cause that got awkward with "how many times do I need to wrap this in a list?" unless I would do all params as a seperate function.