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
I'm working on a project that needs to do something similar to cover, where it finds lists of modules given packages or collections and filters the list based on info.rkt settings. Would it be worthwhile to try and extract cover's implementation of this logic into a package I could reuse?
The text was updated successfully, but these errors were encountered:
jackfirth
changed the title
Extract package modules code?
Extract package module filtering code?
Aug 31, 2017
Are you refering to https://github.com/florence/cover/blob/master/cover/raco.rkt#L326 or to the horrible mess of https://github.com/florence/cover/blob/master/cover/raco.rkt#L200?
I think the answer is yes to both, but more so for the second one. I know raco test needs to implement something similar (Some bits of this code were cargo-culted from raco test at some point, but I can't remember which is and which isn't anymore...)
I'm working on a project that needs to do something similar to cover, where it finds lists of modules given packages or collections and filters the list based on
info.rkt
settings. Would it be worthwhile to try and extract cover's implementation of this logic into a package I could reuse?The text was updated successfully, but these errors were encountered: