You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Considering the number of commits since then it is safe to say that doc/tests is outdated. Either this area needs to be updated (and likely converted to something other than SGML) or it should be removed.
The text was updated successfully, but these errors were encountered:
I'm in favor of removing it. I don't think it would be worth the effort to maintain the documentation, since the way it is written now it seems to be bound closely with the implementation, which means it would both require frequent updates and largely duplicate what can be read from the code directly.
That's fine. Might want to skim through quickly and see if anything from it ought to be copied to the README or added as an open issue. The most important part of it originally was the coverage tables to show what was being tested but that's long since obsolete and I believe we have created GH issues for known gaps in the current testsuite.
Works for me. I would second @stephensmalley's comment about making sure everything relevant is captured before removing the file.
Of course the nice thing about revision control is that even if we remove the file, it is never really "gone" if we decide we need some information from it.
Considering the number of commits since then it is safe to say that
doc/tests
is outdated. Either this area needs to be updated (and likely converted to something other than SGML) or it should be removed.The text was updated successfully, but these errors were encountered: