Feature request: Opaque/nominal types

The problem

It often happens that library functions return objects the type of which is an implementation detail. For example an identifier may be an integer but could suddenly be changed to a string, and the client code shouldn't fail because of that.

Safely typing such an identifier in LLS is currently impossible:

• typing it as integer depends on a potentially unstable implementation detail
• typing it as any is unsound

In other words, structural typing fails when the structure isn't stable or known.

Feature request

An annotations that declares a completely opaque/nominal type. It could be --@opaque typename, --@alias typename without any arguments, or anything else. Values belonging of such a type cannot be inspected in any way and can only be passed around. Values of different opaque types cannot be mixed up (so this is stronger than unknown in typescript)

Aucun fichier, test ou point d’entrée n’est nommé. Commencez par localiser le code d’annotation et de vérification des types pour les alias et les types inconnus, puis suivez la manière dont les valeurs sont inspectées ou mélangées. Le travail est terminé lorsque le language server prend en charge des types opaques distincts qui peuvent uniquement être transmis, avec une couverture pour le comportement demandé.