Category talk:Go: Difference between revisions
Content added Content deleted
(→In general, non-solutions: trans) |
(→Exceptions/Catch an exception thrown in a nested call: Task name is not full description of task.) |
||
Line 47: | Line 47: | ||
One totally contrived solution would be to make the second call to bar from within the deferred function. I think most anyone would cry foul at that. |
One totally contrived solution would be to make the second call to bar from within the deferred function. I think most anyone would cry foul at that. |
||
: It strikes me as plausibly appropriate you raise this issue in the task page, and suggest that the task be renamed. It sounds like either a better name for the task might be "Recover from a thrown exception", or that the task should perhaps be adjusted to more cleanly reflect a core intent. --[[User:Short Circuit|Michael Mol]] 02:26, 30 April 2011 (UTC) |
: It strikes me as plausibly appropriate you raise this issue in the task page, and suggest that the task be renamed. It sounds like either a better name for the task might be "Recover from a thrown exception", or that the task should perhaps be adjusted to more cleanly reflect a core intent. --[[User:Short Circuit|Michael Mol]] 02:26, 30 April 2011 (UTC) |
||
:: OK, with hindsight, the task might be better ''described'' as "Exceptions/Catch one of two exceptions thrown in a nested call"; but it is unwieldly for a title. I think the title is not misleading, just a precis of the task requirements. |