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

nodemap is virtually untested #370

Open
zoffixznet opened this issue Dec 20, 2017 · 6 comments
Open

nodemap is virtually untested #370

zoffixznet opened this issue Dec 20, 2017 · 6 comments

Comments

@zoffixznet
Copy link
Contributor

I see a single test for nodality and no other tests at all.

We also appear to have this method fully documented: https://docs.perl6.org/routine/nodemap

@zoffixznet
Copy link
Contributor Author

On second glance, this routine is actually used under the hood by the hyper nodal method calls. So the routine is tested as far as weeding out its bugs goes, but perhaps underspecced in a sense that the roast won't cover implementations that don't implement their hyper nodal methcalls using this routine.

@lizmat
Copy link
Contributor

lizmat commented Dec 20, 2017 via email

@zoffixznet
Copy link
Contributor Author

One could consider it more or less an internal method at this stage, imo

Do you think it should be removed from the docs then? Seems to be unused in the ecosystem

(somewhat related Issue on writing extra docs for XXXmap methods: Raku/doc#1720 )

@lizmat
Copy link
Contributor

lizmat commented Dec 20, 2017 via email

@zoffixznet
Copy link
Contributor Author

I’ll leave that decision up to jnthn TimToady.

@jnthn @TimToady ping: should nodemap be considered an internal method and removed from docs (and also likely moved into Rakudo::Internal to handle the nodal hyper method calls)?

@zoffixznet
Copy link
Contributor Author

https://irclog.perlgeek.de/perl6-dev/2017-12-20#i_15604510

jnthn | My recollection in this area is that some years back (pre-6.c), TimToady looked at the various meta-op guts impl functions we had and concluded that they should be public and given public names. produce (the function form of the [...] metaop) appeared at that time as a result of this
| iirc, nodemap/hypermap/deepmap came around this time
| And so were indeed intended as public

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