Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a reason / is not exported? #157

Closed
tfiers opened this issue Jan 11, 2022 · 3 comments
Closed

Is there a reason / is not exported? #157

tfiers opened this issue Jan 11, 2022 · 3 comments

Comments

@tfiers
Copy link

tfiers commented Jan 11, 2022

I would assume there's no danger of conflict due to Julia's dispatch.

@rofinn
Copy link
Owner

rofinn commented Jan 11, 2022

It's not exported because the behaviour / in the context of filepaths is completely different then how it's defined in base. The argument made by core Julia devs is that we'd be randomly changing the meaning of / just by having FilePathsBase loaded in your environment. As a compromise, we've defined it as a completely separate unexported function that falls back to Base./. For reference, here's the original issue that triggered the change.

#53

@rofinn rofinn closed this as completed Jan 11, 2022
@tfiers
Copy link
Author

tfiers commented Jan 12, 2022

thanks for the pointer!
And for the great package :)

@tfiers
Copy link
Author

tfiers commented Apr 3, 2022

Just for future reference and understanding (based on Jeff Bezanson's point 3 here):
If I understand correctly, the reason it is not desired to have /(::AbstractPath, …) exported by default,
is that this would cause all code using / to have longer compilation times.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants