You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They should use something like what Go does for imported names.
Go uses the last name in the package path plus the actual name (fmt.Sprintf or http.Server), which avoids duplication on the actual name.
For example, a task for organizing the Queue would today be called "Organize the Queue", because just "Organize" would be too generic when put on a plan. However, if it was on a topic names "Queue" and its display name was "Queue::Organize", it would be clear and concise.
The trick, however, is that the 'package name' might be the topic or the parent task ...
The text was updated successfully, but these errors were encountered:
They should use something like what Go does for imported names.
Go uses the last name in the package path plus the actual name (fmt.Sprintf or http.Server), which avoids duplication on the actual name.
For example, a task for organizing the Queue would today be called "Organize the Queue", because just "Organize" would be too generic when put on a plan. However, if it was on a topic names "Queue" and its display name was "Queue::Organize", it would be clear and concise.
The trick, however, is that the 'package name' might be the topic or the parent task ...
The text was updated successfully, but these errors were encountered: