MIT/GNU Scheme - Bugs: bug #28370, hash tables should be strong...

Group

Main
- Main
- View members
- Search
Homepage
Download
Support
- Submit new
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
Mailing lists
Source code
Bugs
- Submit new
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
Tasks
- ~~Submit new~~
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
Patches
- ~~Submit new~~
- Browse
- Reset to open
- Digest
- Dependencies
- ~~Export~~
- Get statistics
- Search
News
- Browse
- Atom feed
- ~~Submit~~
- ~~Manage~~

bug #28370: hash tables should be strong unless explicitly desired otherwise

Submitter:	Taylor R. Campbell <riastradh>
Submitted:	Mon 21 Dec 2009 11:34:39 PM UTC


Category:	runtime	Severity:	3 - Normal
Priority:	5 - Normal	Item Group:	Suboptimal behavior
Status:	None	Privacy:	Public
Assigned to:	None	Originator Name:
Open/Closed:	Open
Keywords:

* Mandatory Fields

Add a New Comment Rich Markup

Thu 30 May 2013 09:48:59 PM UTC, comment #2: Not until we have a reasonable story for namespacing so that applications can ask for the hash-table-v2 API rather than just live in a child of the system global environment...	Taylor R. Campbell <riastradh>
Thu 30 May 2013 04:42:11 PM UTC, comment #1: When CAN we change MAKE-EQ-HASH-TABLE to return strong hash tables?	Matt Birkholz <mhb>
Mon 21 Dec 2009 11:34:39 PM UTC, original submission: If one asks for a hash table, one should not get a weak hash table unless one explicitly asked for it. MAKE-EQ-HASH-TABLE and MAKE-EQV-HASH-TABLE currently confusingly yield strong hash tables, as a consequence of which only a small fraction of their uses in MIT Scheme actually needed key-weak hash tables, while for a much large fraction, using key-weak hash tables was either confusing or incorrect. We can't change the semantics of these two procedures immediately, however, because what they do now is what they have been documented to do. See discussion at <http://lists.gnu.org/archive/html/mit-scheme-devel/2009-12/msg00032.html>. Use of MAKE-EQ-HASH-TABLE was eradicated from MIT Scheme in commit da6830c165b2540d93d1e3f1b31b6f0470392868, replaced by use of the more specific constructors MAKE-STRONG-EQ-HASH-TABLE and MAKE-WEAK-EQ-HASH-TABLE.	Taylor R. Campbell <riastradh>

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:


Comment:

No files currently attached

Depends on the following items: None found

Items that depend on this one: None found

Carbon-Copy List

-email is unavailable- added by mhb (Posted a comment)

-email is unavailable- added by mhb

-email is unavailable- added by riastradh (Submitted the item)

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

Please enter the title of George Orwell's famous dystopian book (it's a date):

Follows 1 latest change.

Date	Changed by	Updated Field	Previous Value	=>	Replaced by
2013-05-30	mhb	Carbon-Copy	-		Added -email is unavailable-

MIT/GNU Scheme - Bugs: bug #28370, hash tables should be strong...

bug #28370: hash tables should be strong unless explicitly desired otherwise

<a href="#postcomment">Post a Comment</a>

<a href="#discussion">Discussion</a>

<a href="#attached">Attached Files</a>

<a href="#dependencies">Dependencies</a>

<a href="#cc">Mail Notification Carbon-Copy List</a>

<a href="#votes">Votes</a>

<a href="#history">History</a>