
Wow, I did not realize this was the behavior. I would consider it a major bug.
+1 to removing, -1 to any deprecation periods or delay, +0 to adding the existing function with a new name (as long as warnings are clearly visible)
I would also support backporting a warning to haddocks for versions before the "fix"
Tom
El Jan 5, 2015, a las 18:44, Brandon Allbery
On Mon, Jan 5, 2015 at 5:54 PM, Johan Tibell
wrote: Aside: can we look at what other languages with similar functions do?
You will find that essentially all other implementations do the right thing and not follow symlinks, because the other behavior is a severe bug. I really do not understand why anyone believes the current behavior is defensible.
-- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries