Which statements about Gosu methods are correct?

The focus on restricting the scope of methods to what is essential aligns with best practices in programming, particularly in object-oriented design. This principle promotes encapsulation and clarity, making it easier to maintain and understand code. By limiting a method's responsibilities, developers can enhance reusability and minimize side effects, ensuring that each method achieves a specific purpose without unnecessary complexity.

In contrast, using noun-based names for methods may not always be appropriate, as methods are typically actions and are usually named with verbs reflecting what they do (e.g., calculateTotal, retrieveData). While it's true that a method might have a clear responsibility, naming conventions should emphasize the action rather than the result.

There is also flexibility in method visibility; while public methods are common, it’s not a requirement that all methods must be public. Methods can also be private or protected based on the desired encapsulation level.

Lastly, in Gosu, as in many programming languages, a method cannot return multiple values like a tuple in some other languages. Instead, methods typically return a single value, and if multiple outputs are needed, they are often returned via an object or a collection.

Overall, the importance of scope reflects a significant aspect of software design principles, supporting more organized