Why do we have cached results?
Beginners do something like
for x in small_list:
if x in SimpleThing(42).list():
echo("Found!", x)
Advanced users should know how to do
temp = ComplicatedThing(10^6).list()
matches = [x for x in big_list if x in temp]
So when is caching results usefu
On Thu, Jun 2, 2016 at 9:45 PM, Kwankyu Lee wrote:
>> Suppose that our object X has a basis consisting of four 2x2 matrices,
>> in some abstract sense. Then your
>>
>>X.list()
>>
>> might very well return a tuple of four *mutable* 2x2 matrices. Then
>> this X.tuple() is still very much muta
Hi,
Sagemath7.2 fails to compile from source on Debian 8.4. It gives the
following error:
configure: error: in `/home/seyi/sage/7.2/source/sage-7.2':
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
If you would like to try to build Sage anyway (t
On Thursday, 2 June 2016 16:39:53 UTC-6, paulmasson wrote:
>
> Andrey, any idea when my embedded interacts will start working again?
> Thanks.
>
Hopefully by Monday. I still don't know what exactly is happening, but I
didn't work much on it since last weekend was short on time in general and
I
>
> Suppose that our object X has a basis consisting of four 2x2 matrices,
> in some abstract sense. Then your
>
>X.list()
>
> might very well return a tuple of four *mutable* 2x2 matrices. Then
> this X.tuple() is still very much mutable, and the original problem
> has not been solved
Andrey, any idea when my embedded interacts will start working again?
Thanks.
On Monday, May 23, 2016 at 9:28:35 PM UTC-7, Andrey Novoseltsev wrote:
>
> On Sunday, 22 May 2016 15:27:26 UTC-6, paulmasson wrote:
>>
>> Still getting the problem. Occurs on about half of page loads right now.
>>> Her
On Thu, Jun 2, 2016 at 1:33 PM, Volker Braun wrote:
> I'm guessing that this won't fly with upstream ;-)
>
> Is it really faster? A new __unary_div__ method everywhere? Is it really
> faster than special-casing the 1/x case in __div__?
According to my unscientific benchmark just now there seems
On Thu, Jun 2, 2016 at 1:39 PM, Volker Braun wrote:
> On Thursday, June 2, 2016 at 5:34:49 PM UTC+2, William wrote:
>>
>> (1) No matter your grammar argument about deficiencies in the
>> technical language, it's a fact that the majority of English speakers
>> is going to consider this confusing.
On Thursday, June 2, 2016 at 5:34:49 PM UTC+2, William wrote:
>
> (1) No matter your grammar argument about deficiencies in the
> technical language, it's a fact that the majority of English speakers
> is going to consider this confusing.
>
The majority of English speakers will be perfectly un
I'm guessing that this won't fly with upstream ;-)
Is it really faster? A new __unary_div__ method everywhere? Is it really
faster than special-casing the 1/x case in __div__?
Also, /x/ is a regular expression in JS. If Python ever wanted to support
that syntax then this would be stepping on th
On 2016-06-02 17:17, William Stein wrote:
have an explicit method (e.g., .multiplicative_inverse())?
That's bad for several reasons:
1. Python types won't support it. This new operator is meant to increase
compatibility between Sage and Python. I think it's very unlikely that
Python types wil
Hi!
On 2016-06-02, William Stein wrote:
> F.list()
>
> should return a new list each time just like list(F) does.
+1
For efficiency, we might have a version of @cached_method which does
store a version of the output once it is computed, but does not directly
return what it's in store. Instead,
On Thu, Jun 2, 2016 at 1:46 AM, Volker Braun wrote:
> No, generally method names are verbs and class names are nouns. There is no
> verb for "making a tuple" which is a bit of a deficiency in the English
> language if anything; But all those linguistic details pale in comparison to
> the glaring h
Hi,
Obviously I screwed up and just assumed, as a mathematician, that a
method called
__invert__
would be for computing the inverse of something.There is no sense
in which the bitwise version of that is the mathematical inverse of
an *integer*, so I didn't even consider that possibility.
On 2016-06-02 15:52, Erik Bray wrote:
1. If flipper makes heavy use of bitwise negation then to prevent
errors should explicitly cast values to a type where ~x means bitwise
negation and not reciprocal (or anything else) in the first place.
No because it's not only in the Flipper program itself
On Thu, Jun 2, 2016 at 2:01 PM, Jeroen Demeyer wrote:
> Summary: Python should have a unary division operator (a.k.a. reciprocal),
> written "/x", analogous to unary subtraction (a.k.a. negation), written
> "-x". And then "~x" should be what is intended by Python, namely bitwise
> negation.
>
> Ra
On Thursday, June 2, 2016 at 7:23:57 AM UTC-5, Samuel Lelievre wrote:
>
>
> 2016-06-02 14:01:16 UTC+2, Jeroen Demeyer:
>>
>> Summary: Python should have a unary division operator (a.k.a.
>> reciprocal), written "/x", analogous to unary subtraction (a.k.a.
>> negation), written "-x". And then "~x
2016-06-02 14:01:16 UTC+2, Jeroen Demeyer:
>
> Summary: Python should have a unary division operator (a.k.a.
> reciprocal), written "/x", analogous to unary subtraction (a.k.a.
> negation), written "-x". And then "~x" should be what is intended by
> Python, namely bitwise negation.
>
> Rationa
Summary: Python should have a unary division operator (a.k.a.
reciprocal), written "/x", analogous to unary subtraction (a.k.a.
negation), written "-x". And then "~x" should be what is intended by
Python, namely bitwise negation.
Rationale: Mark Bell gave a talk at Sage Days 74 and he mentione
See also http://trac.sagemath.org/ticket/10927
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send
No, generally method names are verbs and class names are nouns. There is no
verb for "making a tuple" which is a bit of a deficiency in the English
language if anything; But all those linguistic details pale in comparison
to the glaring hole of caching mutable results.
On Thursday, June 2, 2
21 matches
Mail list logo
