Kaydet (Commit) 6f19fc6d authored tarafından Robert Krzyzanowski's avatar Robert Krzyzanowski Kaydeden (comit) Tal Einat

fix two typos in Objects/odictobject.c comments (GH-8040)

üst c929df3b
...@@ -67,7 +67,7 @@ Linked-List API ...@@ -67,7 +67,7 @@ Linked-List API
As noted, the linked-list implemented here does not have all the bells and As noted, the linked-list implemented here does not have all the bells and
whistles. However, we recognize that the implementation may need to whistles. However, we recognize that the implementation may need to
change to accommodate performance improvements or extra functionality. To change to accommodate performance improvements or extra functionality. To
that end, We use a simple API to interact with the linked-list. Here's a that end, we use a simple API to interact with the linked-list. Here's a
summary of the methods/macros: summary of the methods/macros:
Node info: Node info:
...@@ -444,7 +444,7 @@ Potential Optimizations ...@@ -444,7 +444,7 @@ Potential Optimizations
- Set node->key to NULL to indicate the node is not-in-use. - Set node->key to NULL to indicate the node is not-in-use.
- Add _odict_EXISTS()? - Add _odict_EXISTS()?
- How to maintain consistency across resizes? Existing node pointers - How to maintain consistency across resizes? Existing node pointers
would be invalidate after a resize, which is particularly problematic would be invalidated after a resize, which is particularly problematic
for the iterators. for the iterators.
* Use a more stream-lined implementation of update() and, likely indirectly, * Use a more stream-lined implementation of update() and, likely indirectly,
__init__(). __init__().
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment