Suggestion: #error directive

[zpdDG4gta8XKpMCd]

C# and C++ have a handy #error directive that results to a compiler error. It would not hurt to have something similar in TypeScript:

• https://msdn.microsoft.com/en-us/library/c8tk0xsk.aspx
• https://msdn.microsoft.com/en-us/library/x5hedts0.aspx

[mhegazy]

Can you share a scenario where this is useful in the absence of conditional compilation using preprocessor directives (i.e. #ifdef)

[zpdDG4gta8XKpMCd]

Any block of code that is left unfinished during refactoring and requiring
my attention. An alternative would be to leave it unfinished without a
trace attracting attention and thus prone to being forgotten.
On Jun 19, 2015 5:33 PM, "Mohamed Hegazy" [email protected] wrote:

Can you share a scenario where this is useful in the absence of
conditional compilation using preprocessor directives (i.e. #ifdef)

—
Reply to this email directly or view it on GitHub
#3575 (comment)
.

[zpdDG4gta8XKpMCd]

A error raised should not be an early one like those of syntax, should be raised while doing senatic checking.

[danquirk]

Is // TODO (and an editor supporting task lists) and "throw new Error('not yet implemented')" that much worse? You lose a little compile time checking but little else. You could also use a linter to catch this kind of thing at compile time with some custom tag (// #error).

[zpdDG4gta8XKpMCd]

True. Anything can be done with extra syntax served in comments and a
little patience. With a bit more patience a pen and a piece of paper one
can get a hard copy of their todo list. Low tech shoots and scores.
On Jun 19, 2015 7:26 PM, "Dan Quirk" [email protected] wrote:

Is // TODO (and an editor supporting task lists) and "throw new Error('not
yet implemented')" that much worse? You lose a little compile time checking
but little else. You could also use a linter to catch this kind of thing at
compile time with some custom tag (// #error).

—
Reply to this email directly or view it on GitHub
#3575 (comment)
.

[zpdDG4gta8XKpMCd]

Btw are there any plans to marry TypeScript with the Task list in Visual
Studio, so that // TODO's are seen there?
On Jun 19, 2015 8:14 PM, "Aleksey Bykov" [email protected] wrote:

True. Anything can be done with extra syntax served in comments and a
little patience. With a bit more patience a pen and a piece of paper one
can get a hard copy of their todo list. Low tech shoots and scores.
On Jun 19, 2015 7:26 PM, "Dan Quirk" [email protected] wrote:

Is // TODO (and an editor supporting task lists) and "throw new
Error('not yet implemented')" that much worse? You lose a little compile
time checking but little else. You could also use a linter to catch this
kind of thing at compile time with some custom tag (// #error).

—
Reply to this email directly or view it on GitHub
#3575 (comment)
.

[danquirk]

Yep, VS2015 already has the Task List wired up like that.

[mhegazy]

Any block of code that is left unfinished during refactoring and requiring
my attention.

you can just use unknownFunction("not done"), or var n: number = "still needs some work"; to achieve the same result.

[mhegazy]

possibly reconsider if an applicable form of conditional compilation (#3538) is supported.