Is it feasible to qualify imports from Prelude?

[JustusAdam]

Problem

I happen to use Alex in a context where I have a custom Prelude and also
warnings enabled for the use of undefined and to top things off I use
--pedantic when compiling on CI.

So basically its a bit inconvenient.

My question therefore is would it not be better perhaps to only use fully
qualified imports and fully qualified names in the templates/lexers to avoid
potential clashes with user imports/defines?

Solution

Because this is a very minor issue I'd happily take it upon myself to
"implement" it, so long as there are no objections.

[simonmar]

Yes, I think this would be good. I'll gladly accept a PR that fully qualifies everything.

[andreasabel]

@JustusAdam Would you still be up for this?
I added qualification for all non-Prelude imports in:

• Generate _qualified_ imports to avoid clashes with user code #259