News for hackers. Stuff that matters.

A comment on Why we’re writing machine learning infrastructure in Go, not Python. Parent comment

Re:Why we’re writing machine learning infrastructure in Go, ... by sagichmal on Sunday January 19, 2020 @03:41PM (#22093904)
> no incremental compilation

Not true, unless you're using an esoteric definition of "incremental".

> imports don't support cyclic imports

Why on earth would you consider this bad?

[ Parent | on HN ]
Re:Why we’re writing machine learning infrastructure in Go, ... by qtplatypus on Sunday January 19, 2020 @11:29PM (#22096306)
The problem that I've ran into with the lack of cyclic imports is that I like to arrange the contents of packages logically. However sometimes in order to do this it would result in a circular dependency between two packages. So rather then getting a logical arrangement we have to refactor it into an artificial package to resolve this depenancy.
[ Parent | on HN ]
Re:Why we’re writing machine learning infrastructure in Go, ... by sagichmal on Monday January 20, 2020 @04:16AM (#22097546)
Circular imports are always a design error, no "logical" to it.
[ Parent | on HN ]