We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From API proposal #25173.
Need to add:
namespace System.IO { public static class Path { public static bool TryGetTempPath(Span<char> destination, out int charsWritten); } }
Returns false if the destination isn't large enough to fit the full path into.
The text was updated successfully, but these errors were encountered:
@JeremyKuhne if you want i can start with this, feel free to assign to me
Sorry, something went wrong.
@JeremyKuhne Do we have examples of where the no-allocation version of this API makes a difference?
You are about to create a temporary file. Creating a temporary file is orders of magnitude more expensive operation than just allocating a string.
I think the no-allocation version of these APIs are adding negative value to the platform.
(Add Path.TryGetRelativePath() and Path.TryGetFullPath() are fine.)
Path.TryGetRelativePath()
Path.TryGetFullPath()
Video
Closing for now until we re-review the API proposal.
MarcoRossignoli
No branches or pull requests
From API proposal #25173.
Need to add:
Returns false if the destination isn't large enough to fit the full path into.
The text was updated successfully, but these errors were encountered: