Re: [w3c/IndexedDB] Clarify the handling of +0 and -0 in keys (Issue #375)

Apologies for the delay, I've been OOO for a bit.

> Generally I think the normalization would simplify the spec and implementation, i.e. we can always assume no -0 in keys. But with existing implementation we have, that probably means we need to convert -0 in database to 0 after the spec change. How is Blink going to deal with this? @inexorabletash

@szewai - In Blink, all internal key comparisons treat -0 and 0 the same. The patch just ensures that when doing a key-to-JS conversion any -0 is mapped to +0. Whatever was previously stored in the database gets "fixed" on retrieval. This only happens to keys, not values. I can't think of a case that doesn't cover, but I may be missing something.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/375#issuecomment-1285916491
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/375/1285916491@github.com>