Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re^4: [Raku] Ranges in array slices

by holli (Abbot)
on Jun 05, 2021 at 19:20 UTC ( #11133563=note: print w/replies, xml ) Need Help??

in reply to Re^3: [Raku] Ranges in array slices
in thread [Raku] Ranges in array slices

I'm not sure what you're trying to say. This sequence (of even numbers) however will never end.

0,  * + 2  ... 1

If that's what you want to say, then it better be written as

0, 2 ... * or
0, 2 ... Inf


You can lead your users to water, but alas, you cannot drown them.

Replies are listed 'Best First'.
Re^5: [Raku] Ranges in array slices
by tomasz (Acolyte) on Jun 05, 2021 at 20:46 UTC
    To make sure, we're on the same page, the sequence of even numbers can end:
    > say 0, * + 2 ... $_ for 2, 10 (0 2) (0 2 4 6 8 10)
    And if this was obvious, then - yes, that's the point. Sequences allow this kind of dissonances. No error is reported by the language. There's space for absurd. Or what should this be better called?
      I see no dissonance or absurdity here. The code creates two Sequences in a loop and they end because the end conditions (2 and 10) (the thing to the right of ....) get reached.
      If you create a sequence like 0, * + 2 ... 1 where the values go up and the end value is smaller than even the first calculated value, then that Seq. will can never end.


      You can lead your users to water, but alas, you cannot drown them.
Re^5: [Raku] Ranges in array slices
by tomasz (Acolyte) on Jun 06, 2021 at 11:40 UTC
    I think we all agree here on what's what and there's no point to argue about. I'll however continue my line of thinking just as a lighthearted musing.

    It's a language feature and so if there is an error, it will be a semantic error. Or possibly not, as this feature can be productively exploited.

    For example, let's take a hard to calculate number N and use it as the last element condition. And for the generator function let's use a G, and some S for the starting point. Here' the formula:
    S, G ... N
    So we're testing N against G for S. As the test duration can explode towards infinity, we need to limit the number of steps or the time of our test. Let's name this limitation "<<< L" in pseudocode:
    S, G ... N <<< L
    If the test doesn't end before L, we could consider this a proof of absurdity (or semantic errorness) of "S, G ... N" relative to L. And isn't this absurdity similar to infinity of N? Couldn't we say N is infinite relative to S, G, L?

    EDIT: This would be valid for easily computable Ns also. We could say: 1 is infinite relative to 0, * + 2, any L.
      If that is absurd then

      while N <<< L: G = G of S

      is absurd too. The right hand side of ... is just a condition, nothing more. If you're saying that things get absurd when the condition is so expensive that it dwarfs the loop body, then yeah. But then your code is bad, not the semantics of the language.

      I might be still be missing the point, though.


      You can lead your users to water, but alas, you cannot drown them.
        I never meant the semantics of the language itself. Only of the code. I mentioned its syntax though. And yes - bad code, that's it. What is absurd anyways if not a distortion, an error?

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11133563]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (4)
As of 2021-09-17 08:12 GMT
Find Nodes?
    Voting Booth?

    No recent polls found