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 recently observe in https://github.com/aherrmann/rules_zig/ that the toolchain is managed via a rule called zig_repository, which follow the template convention of mylang_repository.
However, what I am used to in Go is go_repository is used to manage 3rd party dependency import. Toolchain in Go is managed via go_{download,local,host}_sdk and go_register_toolchains rules instead.
So I would suggest renaming mylang_repository to mylang_sdk and mylang_register_toolchains while reserving mylang_repository for respective language's 3rd party import. WDYT?
The text was updated successfully, but these errors were encountered:
I recently observe in https://github.com/aherrmann/rules_zig/ that the toolchain is managed via a rule called
zig_repository
, which follow the template convention ofmylang_repository
.However, what I am used to in Go is
go_repository
is used to manage 3rd party dependency import. Toolchain in Go is managed viago_{download,local,host}_sdk
andgo_register_toolchains
rules instead.So I would suggest renaming
mylang_repository
tomylang_sdk
andmylang_register_toolchains
while reservingmylang_repository
for respective language's 3rd party import. WDYT?The text was updated successfully, but these errors were encountered: