It is clearly a compiler bug, and it was introduced in C# 3.0 — right around the time that I heavily refactored the reachability checker. This is probably my bad, sorry. The bug is completely benign; basically, we just forgot a case in the warning reporter. We generate the reachability information correctly; as others have … Read more
You can use err.code const error = new Error(“message”) error.code = “YOUR_STATUS_CODE” throw error;
Yes. The exception is active until it’s caught, where it becomes inactive. But it lives until the scope of the handler ends. From the standard, emphasis mine: ยง15.1/4: The memory for the temporary copy of the exception being thrown is allocated in an unspecified way, except as noted in 3.7.4.1. The temporary persists as long … Read more
It makes no sense to throw an exception in a try block and immediately catch it, unless the catch block throws a different exception. Your code would make more sense this way: public Response getABC(Request request) { Response res = new Response(); if (request.someProperty == 1) { // business logic } else { res.setMessage(“xxxx”); } … Read more
The syntax error is showing up because the previous statement hasn’t been terminated. The other answers will work, but in order to do it this way you can either throw a semicolon right before the THROW, or get in the habit of terminating all statements with semicolons. IF (@val is null) BEGIN ;THROW 50001, ‘Custom … Read more
throw Object.assign( new Error(myMessage), { code: 402 } ); Throw a regular error and extend it with custom fields. You could also write a reusable error class for that: class CodeError extends Error { constructor(message, code) { super(message); this.code = code; } } throw new CodeError(myMessage, 404); That way, you can distinguish the errors easily … Read more
My rule of thumb: Exceptions are used for run-time error conditions (IO errors, out of memory, can’t get a database connection, etc.). Assertions are used for coding errors (this method doesn’t accept nulls, and the developer passed one anyway). For libraries with public classes, throw exceptions on the public methods (because it makes sense to … Read more
If you don’t need to adjust the exception type, you rethrow (throw further) the same instance without any changes: catch (IOException e) { throw e; } If you do need to adjust the exception type, you wrap e (as a cause) into a new exception of the type required. catch (IOException e) { throw new … Read more
Throwing twice in the same method is probably a special case – I’ve not been able to create a stack trace where different lines in the same method follow each other. As the word says, a “stack trace” shows you the stack frames that an exception traversed. And there is only one stack frame per … Read more
The error There are multiple modules with names that only differ in casing. is indicating the wrong import is being targeted with how you are trying to use Observable. The import should be with a capital “O” like: import { Observable } from ‘rxjs/Observable’; This will import the individual Observable operator, which be used in … Read more