#18813: New decoding structure for linear codes
-------------------------+-------------------------------------------------
Reporter: | Owner:
dlucas | Status: needs_review
Type: | Milestone: sage-6.10
enhancement | Resolution:
Priority: major | Merged in:
Component: | Reviewers:
coding theory | Work issues:
Keywords: | Commit:
Authors: David | ddd1eb1f28e3d34dfc83a8ae401495b7cad432b8
Lucas | Stopgaps:
Report Upstream: N/A |
Branch: |
u/dlucas/decoder |
Dependencies: |
#18376 |
-------------------------+-------------------------------------------------
Comment (by dlucas):
"XORing" hash(Str) twice is a mistake, it should (and will) be `[...] ^
hash(G) ^ hash(Str)`.
Regarding the motivation behing the xor, I did as advised in
[https://docs.python.org/2.7/reference/datamodel.html#object.__hash__
Python doc] crossed with this useful (imho) question on
[http://stackoverflow.com/questions/2909106/python-whats-a-correct-and-
good-way-to-implement-hash stack overflow]
>it is advised to somehow mix together (e.g. using exclusive or) the hash
values for the components of the object that also play a part in
comparison of objects.
--
Ticket URL: <http://trac.sagemath.org/ticket/18813#comment:26>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
