because somebody registered package named 'dutils' on dub registry and now it collides with my local package with same name.
Thread overview | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
December 23, 2022 imports like in Go. to avoid package naming collisions [feature request] | ||||
---|---|---|---|---|
| ||||
December 23, 2022 Re: imports like in Go. to avoid package naming collisions [feature request] | ||||
---|---|---|---|---|
| ||||
Posted in reply to AnimusPEXUS | The solution that has been in consideration for a number of years now is name spacing based upon account. But no one has implemented yet. |
December 25, 2022 Re: imports like in Go. to avoid package naming collisions [feature request] | ||||
---|---|---|---|---|
| ||||
Posted in reply to AnimusPEXUS | On Friday, 23 December 2022 at 03:56:08 UTC, AnimusPEXUS wrote: >because somebody registered package named 'dutils' on dub registry and now it collides with my local package with same name. I think I've came up with some collision avoid decision: I'll calc CRC for my 'github.com/AnimusPEXUS' profile and will use it like so: 'p315cffe8_packagename' so all my packages will have 'p315cffe8' prefix in names.. or maybe 'crc32_315cffe8_packagename', to define hash method. |
December 25, 2022 Re: imports like in Go. to avoid package naming collisions [feature request] | ||||
---|---|---|---|---|
| ||||
Posted in reply to AnimusPEXUS | On Sunday, 25 December 2022 at 13:13:25 UTC, AnimusPEXUS wrote: >On Friday, 23 December 2022 at 03:56:08 UTC, AnimusPEXUS wrote: >because somebody registered package named 'dutils' on dub registry and now it collides with my local package with same name. I think I've came up with some collision avoid decision: I'll calc CRC for my 'github.com/AnimusPEXUS' profile and will use it like so: 'p315cffe8_packagename' so all my packages will have 'p315cffe8' prefix in names.. or maybe 'crc32_315cffe8_packagename', to define hash method. Why not |
December 25, 2022 Re: imports like in Go. to avoid package naming collisions [feature request] | ||||
---|---|---|---|---|
| ||||
Posted in reply to Siarhei Siamashka | On Sunday, 25 December 2022 at 14:12:11 UTC, Siarhei Siamashka wrote: >On Sunday, 25 December 2022 at 13:13:25 UTC, AnimusPEXUS wrote: >Why not because 315CFFE8 covers whole 'github.com/AnimusPEXUS' which is less likely will change soon. and AnimusPEXUS doesn't (and shouldn't) mean anything to anybody on it's own. |
December 25, 2022 Re: imports like in Go. to avoid package naming collisions [feature request] | ||||
---|---|---|---|---|
| ||||
Posted in reply to Siarhei Siamashka | On Sunday, 25 December 2022 at 14:12:11 UTC, Siarhei Siamashka wrote: >On Sunday, 25 December 2022 at 13:13:25 UTC, AnimusPEXUS wrote: Why not and to avoid cybersquatting on dub repo, I'd rather make and agreement with dub repo's owner to make 'p315cffe8' prefix locked to be used for my packages only. |
December 25, 2022 Re: imports like in Go. to avoid package naming collisions [feature request] | ||||
---|---|---|---|---|
| ||||
Posted in reply to Siarhei Siamashka | On Sunday, 25 December 2022 at 14:12:11 UTC, Siarhei Siamashka wrote: >Why not Gives me something to think about, personally. My nickname does not mean "C compiler", just in case anyone was curious, but I imagine that would still be a bit disorienting if I were to publish modules under it. 😏 |