Reflection of functions with wired-in names leads to errors

[nikivazou]

For example, here: https://gist.github.com/nikivazou/1c134d34830e73c62cc5e18b8b7c8e98

the following assertion fails

{-@ fstBug :: xys:[(a,b)] 
           -> x: {a | member x (fromList (map fst xys))}
           -> () @-}
fstBug :: Ord a => [(a,b)]-> a -> ()
fstBug xys x = assert (member x (fromList (map fst xys))) ()

because the fst in the signature is interpreted as the wired-in fst while the fst in the code as a user-defined fst function. These two are not related.

Proposed Solution: Generate an error when reflecting functions with wired-in names.

[facundominguez]

Assuming wired-in names means names coming from the LH annotations about boot libraries, would it make sense to broaden the focus to any clashes between names in the current module and names coming from annotations in other modules?

[nikivazou]

The example comes from the LH's wired in names
'wiredInNames = S.fromList [ "head", "tail", "fst", "snd", "len"]'. For names imported from different modules, I do not have an opinion. Best to do what GHC is doing.