Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Posts by qohelet
Pros of CLI arguments/flags include: Easier to leverage the tool in another script or via other automation so that user interaction is not required If certain arguments are optional and/or have...
Consider the following posts which have essentially become canonical references in their own right within their respective communities on SE: The Definitive C++ Book Guide and List (viewed 2.5 mil...
I'm completing the rustlings exercises as part of self-teaching Rust. While working on the third iterators exercise, I solved the exercise but don't quite understand why my solution works. Specifi...
How do I create a flag that can be used multiple times in a command using the pflag package? For example, let's say I wanted to select multiple fields and did not want to have to use comma-separati...
Can a Go package name validly contain a hyphen and/or an underscore? The godocs say that By convention, packages are given lower case, single-word names; there should be no need for underscores or...
In Python 2, I was able to create a file named .env within a project folder like so: # .env MY_ID=abc123 TOKEN=4567890 Then in a Python file in the same directory, I could read these variable...
Option 1. The docstring precedes the attributes by convention. Here is an example of the docstring for std::vec::Vec. However, if using cargo doc to generate documentation, it works just fine if y...
When documenting a struct with attributes, where does the docstring go? Before or after the attribute(s)? Option 1: /// Does it go here? #[derive(Deserialize, Debug)] pub struct Metadata { ...
