Cannot use a local scheme file with the same name as a husk library file

[justinethier]

If a file in the local husk directory has the same name as a husk library file (EG: core.scm), then husk will find the local file when searching for the library file. Obviously this causes a lot of internal problems when definitions are not found, etc.

It would be great if husk was smart enough to ignore local files when loading known libraries. Alternatively, the libraries could be given mangled names that would be unlikely to cause a conflict, but that is not ideal.