#iterating on a library

3 messages · Page 1 of 1 (latest)

rapid orchid
#

fair warning, this is probably a dumb question/missing something obvious.

still relatively new to go, been working on a project, have some code separated out into a subfolder with its own package. i would like to spin this out to be its own library, which seems easy to do. from all that i have read, its kinda just work on your library as the top level, and then include it like a normal package elsewhere. perhaps im missing something obvious here, but i would like to include the library as a package, but still be able to work on it(while its required), so that i can test out using it, etc like when its was in a subfolder.

pure lake
#

This will allow you to have a local copy of the module included in your other project, while still being able to work on it independently