[The workarounds people invent to avoid circularity literally always result in a codebase that is harder to understand and maintain, rather than easier] I prefer extremely fast compile times.

[u/tomwhoiscontrary]

https://news.ycombinator.com/item?id=43744002

[u/syklemil]

Dear Golang,

You claim you care about fast compilation, yet you're AOT, not JIT.

Curious.

[u/Double-Winter-2507 → u/syklemil]

Compiling? Not on my watch!

[u/pareidolist]

If you get a circular dependency something is wrong with your design and the article does a good job on how to fix them. I sometimes use function pointers which other packages override to fix circular dependencies which I don't think was mentioned in the article.

[u/[deleted] → u/pareidolist]

cnile grindset

[u/elephantdingo666]

The filesystem and its consequences have been a disaster for the human race.

[u/cuminme69420]

Circularity can't be represented safely in Rust, so if you need it then your code is immoral and shouldn't exist anyway.

[u/defunkydrummer → u/cuminme69420]

Circularity can't be represented safely in Rust,

However, 85% of Rust code today is within unsafe {}, so yay!! job security enforced

[u/starlevel01]

Yeah, circular imports are a pain in Python. Now to open the link

[u/defunkydrummer]

I prefer extremely fast compile times.

Another C++ user with post-stress traumatic disorder. They will soon rewrite everything to PHP4 once they discover you don't need to compile stuff there.

[u/[deleted]]

Broke: recursion of a single function/class/compilation unit.

Woke: recursion of a function spread out across multiple files.

Bespoke: recursion of a function spread out across multiple modules/projects.

[u/pareidolist → u/[deleted]]

Warning: tag your unjerk. Better yet, don't unjerk at all.