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

Move File.readable?, .writable?, .executable? to File::Info #14484

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

straight-shoota
Copy link
Member

Resolves part of #14245

Copy link
Contributor

@ysbaddaden ysbaddaden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering about the policy around deprecated methods and their documentation: shall we keep the doc comment, only have the Deprecated annotation, add a See Type#method link (which maybe the Deprecated annotation could handle)?

@straight-shoota
Copy link
Member Author

It's probably best to keep the current documentation. The method still works like that and deprecation is just a friendly indicator for future changes.

The deprecation message typically refers to the replacement (which is implicitly linked). So there's no need for an explicit See XY.

@crysbot
Copy link

crysbot commented Apr 23, 2024

This pull request has been mentioned on Crystal Forum. There might be relevant details there:

https://forum.crystal-lang.org/t/add-file-info-methods-to-path/6781/1

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

Successfully merging this pull request may close these issues.

None yet

3 participants