Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign updefine safe variant of short_file_name #1067
Conversation
|
I think we once use proper deprecation. We could "tag" the older unsafer variant and say it'll go in, say, 12 month. Thoughts? (That is somewhat orthogonal to the PR though of course not fully...) |
|
I don't have any strong feelings re: deprecation -- I'll let you make the call. I expect removing it would go smoothly, but experience has taught me to always expect surprises. |
Codecov Report
@@ Coverage Diff @@
## master #1067 +/- ##
=======================================
Coverage 95.61% 95.61%
=======================================
Files 64 64
Lines 2782 2782
=======================================
Hits 2660 2660
Misses 122 122
|
Pull Request Template for Rcpp
Closes #1066. This PR comes with two pieces:
A "safe" definition of
short_file_name, defined and used explicitly in theRcpp::debugnamespace;A re-worked version of the "old" (+ registered)
short_file_name, which now uses a static buffer. I believe the method should be effectively un-used but I figured since it's a registered routine it's best to keep the API the same and just silence the compiler warning.Checklist
R CMD checkstill passes all tests