.. but I think it should give an error instead, possibly at the shared-bindings level.

This came up in review of #9995, which includes a special case. When fixing this, remove that code when you do.