In the chat, a user named fubhy reports an issue where the deepStrictEqual function does not work as expected for comparing Option.Option types in TypeScript. Specifically, the comparison fails to distinguish between Option.some("foo") and Option.none(), and incorrectly passes as equal. Fubhy notes that this issue occurs only when comparing with none. Michaelarnaldi suggests checking if matchers have been set up but then realizes this discussion pertains to the effect test suite. Michaelarnaldi mentions that a redesign is planned and suggests potentially addressing this as part of a hackathon.
Key takeaways:
deepStrictEqual has a known issue when comparing Option.Option types, specifically with none.
The issue does not occur with non-none option comparisons.
A redesign is planned, which may address this issue.
The problem could be an opportunity for community contribution, potentially in a hackathon context.
Summary
In the chat, a user named fubhy reports an issue where the
deepStrictEqualfunction does not work as expected for comparingOption.Optiontypes in TypeScript. Specifically, the comparison fails to distinguish betweenOption.some("foo")andOption.none(), and incorrectly passes as equal. Fubhy notes that this issue occurs only when comparing withnone. Michaelarnaldi suggests checking if matchers have been set up but then realizes this discussion pertains to the effect test suite. Michaelarnaldi mentions that a redesign is planned and suggests potentially addressing this as part of a hackathon.Key takeaways:
deepStrictEqualhas a known issue when comparingOption.Optiontypes, specifically withnone.noneoption comparisons.Discord thread
https://discord.com/channels/795981131316985866/1304044332856119296