Darren Duncan wrote
> On 2015-06-16 2:15 PM, The Sidhekin wrote:
> > On Tue, Jun 16, 2015 at 10:52 PM, Michael Zedeler
> > wrote:
> > ...and unpredictable performance is a cost you're willing to pay?
> >
> > I don't write performan
...and unpredictable performance is a cost you're willing to pay?
M.
The Sidhekin wrote
>On Tue, Jun 16, 2015 at 10:02 PM, Michael Zedeler wrote:
>
>I'm not saying that there isn't any alternative to the way other languages
>implements floats, but
gt;
>
>I think Perl 6 tries to include too much rather than too little.
>
>It will be possible to just use a subset
>
>
>On 16 June 2015 at 10:32, Michael Zedeler wrote:
>
>On 06/12/15 15:54, Parrot Raiser wrote:
>
>Has somebody been following the discussions on typ
algorithm in order to be of practical use.
Regards,
Michael.
Aristotle Pagaltzis wrote
>* Michael Zedeler [2015-06-16 18:55]:
>> For instance, why have Complex and Rat numbers in the core? If you're
>> not working in a very specialized field (which probably *isn&
ust use a subset
>>
>> On 16 June 2015 at 10:32, Michael Zedeler wrote:
>>
>>> On 06/12/15 15:54, Parrot Raiser wrote:
>>>
>>>> Has somebody been following the discussions on types?
>>>> http://xkcd.org/1537/ :-)*
>>>>
>&g
Hi Aristotle.
On 06/16/15 12:24, Aristotle Pagaltzis wrote:
* Michael Zedeler [2015-06-16 11:35]:
This is working exactly as specified in the synopsis, but does Perl
6 NEED anything like this? Just because something is possible doesn't
make it an automatic requirement!
Well someone th
ople* has written in that language. I
don't want to maintain anything using this operator (or its twin, .+),
because I haven't seen just one reasonable use case for it.
--
Michael Zedeler
70 25 19 99
mich...@zedeler.dk
dk.linkedin.com/in/mzedeler | twitter.com/mzedeler | github.com/mzedeler
lly sweet.
Regards,
Michael.
--
Michael Zedeler
70 25 19 99
mich...@zedeler.dk
dk.linkedin.com/in/mzedeler | twitter.com/mzedeler | github.com/mzedeler
on't make it the
default.
Written by a seasoned user of a fair amount of programming languages.
--
Michael Zedeler
70 25 19 99
mich...@zedeler.dk <mailto:mich...@zedeler.dk>
dk.linkedin.com/in/mzedeler <http://dk.linkedin.com/in/mzedeler/> |
twitter.com/mzedeler <https:/
On 2014-03-31 14:49, Michael Zedeler. wrote:
On 2014-03-29 21:45, Damian Conway wrote:
Moritz wrote:
To spin the tale further, we need to think about what happens if
somebody writes
multi foo(1|2e0) { ... }
so now we have Int|Num. We could explore the most-derived common
ancestor (Cool), or
ally
typed language is counterproductive :-) ).
In general - Perl (5) is a great tool because it doesn't force people to
deal too much with typing (both implicit and explicit). Lets keep it
that way.
--
Michael Zedeler
70 25 19 99
mich...@zedeler.dk <mailto:mich...@zedeler.dk>
dk
On 2011-08-20 12:02, Damian Conway wrote:
Carl asked:
* What language components could be provided to put class implementors
on the right path so that their classes end up encapsulated by
default?
Doing nothing should result in the safe behaviour (i.e. full encapsulation).
You ought to have to
On 2010-07-31 20:23, Carl Mäsak wrote:
* Today we discovered that it's possible to break encapsulation by
detaching a method from an object of one class, and calling that
method on an object of another class. Which means that breaking the
encapsulation of a foreign class is as easy as creating a
On 2010-07-29 02:19, Jon Lang wrote:
Michael Zedeler wrote:
Jon Lang wrote:
This is definitely something for the Unicode crowd to look into. But
whatever solution you come up with, please make it compatible with the
notion that "aardvark".."apple" can be used
On 2010-07-29 01:39, Jon Lang wrote:
Aaron Sherman wrote:
In smart-match context, "a".."b" includes "aardvark".
No one has yet explained to me why that makes sense. The continued use of
ASCII examples, of course, doesn't help. Does "a" .. "b" include "æther"?
This is where Germans and Swedes,
On 2010-07-29 00:24, Dave Whipp wrote:
Aaron Sherman wrote:
On Wed, Jul 28, 2010 at 11:34 AM, Dave Whipp
wrote:
To squint at this slightly, in the context that we already have
0...1e10 as
a sequence generator, perhaps the semantics of iterating a range
should be
unordered -- that is,
for
On 2010-07-28 06:54, Martin D Kealey wrote:
On Wed, 28 Jul 2010, Michael Zedeler wrote:
Writing for ($a .. $b).reverse -> $c { ...} may then blow up because it
turns out that $b doesn't have a .succ method when coercing to sequence
(where the LHS must have an initial value), j
On 2010-07-27 23:50, Aaron Sherman wrote:
PS: On a really abstract note, requiring that ($a .. $b).reverse be lazy
will put new constraints on the right hand side parameter. Previously, it
didn't have to have a value of its own, it just had to be comparable to
other values. for example:
for $
On 2010-07-16 18:40, Aaron Sherman wrote:
Oh bother, I wrote this up last night, but forgot to send it. Here y'all go:
I've been testing ".." recently, and it seems, in Rakudo, to behave like
Perl 5. That is, the magic auto-increment for "a" .. "z" works very wonkily,
given any range that isn't
yary wrote:
...
Also, the domain should define how to compare objects and could provide
details about whether the set is finite, countable or uncountable.
...
Sounds like a role "Domain" that provides methods (off the top of my head)-
ordering - returns Nil if the domain is unordered,
David Green wrote:
On 2009-Oct-4, at 2:07 pm, Moritz Lenz wrote:
Michael Zedeler wrote:
It doesn't, because succ should always give the next, smallest possible
element given some ordering relation.
Where's that definition from?
The dictionary. =) It would be confusing to have a
Moritz Lenz wrote:
Jon Lang wrote:
How do pred and succ work when given Complex values?
By adding/substracting 1 from the real part, I'd say. Don't know if that
actually makes sense.
It doesn't, because succ should always give the next, smallest possible
element given some ordering
Hi Darren.
Darren Duncan wrote:
In a project of mine I'm looking to use Perl 6 Range values to
represent continuous interval values in the most generic manner
possible, meaning that the endpoint values could literally be of any
type at all. [...] for a realistic example:
my $a = ['Foo', 17
Karl Brodowsky wrote:
Michael Zedeler schrieb:
Well... maybe. How do you specify the intended precision, then? If I
want the values from 1 to 2 with step size 0.01, I guess that writing
1.00 .. 2.00
won't be sufficient. Trying to work out the step size by looking at
the precision of t
Jon Lang wrote:
Michael Zedeler wrote:
Proposed changes:
It shouldn't be possible to construct RangeIterators over Str (apart from
single length strings) or Complex using the Range operator (..).
I'd go one step further with Complex, to say that Range isn't a useful
co
strings) or Complex using the Range operator (..).
Next open question:
What about Ranges using different types in each endpoint?
1.5 .. 10 :by(0.5)
(Rat .. Int)
"0" .. 7
Should they be coerced - and in that case to what? If we don't coerce
them, what should be returned?
Regards,
Michael Zedeler.
James Cloos wrote:
"Michael" == Michael Zedeler writes:
Michael> The Range 1.0001 .. 2.15 makes sense as an interval definition, but
Michael> there can hardly be a useful list definition without defining a step
Michael> size, at least, making it possible to
r option is to provide a completely different operator for
constructing Intervals.
Darren Duncan brought this up before. See
http://osdir.com/ml/perl6-language/2009-02/msg00422.html
Regards,
Michael Zedeler.
28 matches
Mail list logo