taylorswift

tasks: - [x] Refactor `Swiftinit.TagsTable` to have three permissions levels instead of two. Hide admin-only actions from the first two levels. - [x] Show Package ID (not name) under **Package...

here is another example of a broken package link: https://swiftinit.org/docs/ordo-one.package-frostflake

this will be resolved by #198

`swift-png` issue: https://github.com/kelvin13/swift-png/issues/22

i have also found this extremely frustrating although the problem is hardly limited to this particular project. identifying toolchains is hard.

> We had another instance this morning where a node was completely locked up for hours, running swift-backtrace at 100% CPU: i have seen something sporadically similar to this ever...

google prefers stable URLs when selecting canonicals. by definition "latest release" cannot possibly be stable because there will always be new releases. this is a very hard problem.

can you test if this also occurs with 5.6.2? (that is what the CI uses) also, does `-parse-as-library` help?

this is only a breach-of-contract in the generic case; because `UInt8` is a trivial type, it should be perfectly valid to leave the memory uninitialized. i am reluctant to have...

it would be really great if we could suppress the DocC symbol link warnings, those cross-module/cross-package links work on Swiftinit!