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
@climbfuji this is from that video you sent about Spack, and one of the slides mentioned using blacklists_implicits: true. I tried this out myself and it's pretty useful.
Modules will only be generated for explicit (or whitelist:) specs, and then the giant blacklist we have can be cut down. Instead of blacklisting what we don't want, it might be more useful to whitelist what we do want.
The text was updated successfully, but these errors were encountered:
On Jun 10, 2022, at 1:35 PM, Kyle Gerheiser ***@***.***> wrote:
@climbfuji <https://github.com/climbfuji> this is from that video you sent about Spack, and one of the slides mentioned using blacklists_implicits. I tried this out myself and it's pretty useful.
Modules will only be generated for explicit (or whitelist:) specs, and then the giant blacklist we have can be cut down to just what we want.
—
Reply to this email directly, view it on GitHub <#197>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5C2RNUL6CONH5AYJRSLWTVOOKGTANCNFSM5YOUZOOQ>.
You are receiving this because you were mentioned.
@climbfuji this is from that video you sent about Spack, and one of the slides mentioned using
blacklists_implicits: true
. I tried this out myself and it's pretty useful.Modules will only be generated for explicit (or
whitelist:
) specs, and then the giantblacklist
we have can be cut down. Instead of blacklisting what we don't want, it might be more useful to whitelist what we do want.The text was updated successfully, but these errors were encountered: