You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 25fc167
Browse filesBrowse the repository at this point in the historyBrowse files
Accept @notundefined over implementations the compiler cannot see into
Why:
The check rejected bindings that are fine: an interface's
`@notUndefined type t` over `type t = Dom.element`, an abbreviation of an
abstract type, or over a JavaScript object type, which is never
undefined.
An implementation whose representation the compiler does not see has none
that contradicts the interface: an abstract type, also reached through an
abbreviation, or a JavaScript object type. A functor parameter's or a locally
abstract type stands for any type and does not count as abstract.
Diagnostic removed (an abbreviation of an abstract type):
Example:
// A.resi
@notundefined type t
// A.res
type t = Dom.element
Before (diagnostic):
Their runtime representations differ:
the second declaration is @notundefined,
but the first declaration can hold undefined.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CMkrYaktctdKc4M41WF36t
Signed-off-by: Christoph Knittel <ck@cca.io>
0 commit comments