When you import circles in the test file (even if you only select circles_area) the circles file basically gets executed from top to bottom to run all definitions at the point of the import statement. This executes your for loop which fails, and the actual tests are never run. Just remove that loop in the circles module, and it should work.
Gobbel2000
joined 1 year ago
I must say I like the idea of having changes to files be bound to just the current branch, not the entire worktree (section 6.4.2), but other than that the points that are brought up don't really seem too compelling. It certainly didn't convince me that git has an inherently flawed design. For example, eliminating the staging area is a tempting point for simplifying git, but the authors already admit that it has some legitimate use cases.
But of course it is always nice to see some experimentation done in this space. I think the main reason why git sometimes is confusing, is because distributed version control really is a complex task, and git already does a very good job at making it tractable.
Huh? Hexagonal Architecture?
Natürlich! Wo sollen Erdnüsse sonst herkommen, wenn nicht aus der Erde?
While there certainly is some overlap, Python is a scripting language and not a shell language. Some tasks that involve calling lots of different programs and juggling input and output streams are much easier done in bash than in Python.
This blog post goes into some specifics of Rust reusing Vec allocations and some of the consequences. I think it's really worth a read to better understand Vecs. From what I understand, it is possible that Rust will reuse the allocation of vec_a in your case, but it ultimately is quite complicated.
I won't argue with you that bash is janky and easily insecure, but what shell language do you think should replace bash?
Jon Gjengset on Youtube is doing live coding where he uses neovim quite well. And you'll learn about Rust while you're at it.
I'm just glad that type inference can improve this sort of situation a bit:
ConfigManager configManager = new ConfigManager();
I (luckily) haven't had much experience using autotools, but I do suppose it was no coincidence that the injection was initiated there. I really like the comparison that was made in the post of the Meson maintainer you linked:
Several "undefeatable" fortresses have been taken over by attackers entering via sewage pipes.
I enjoy this meme. Truly a Lemmy original.