Hey guys
I just noticed that the alternative listed for the no-void-expression, which, according to the ROADMAP.md-file, is no-void doesn't do the same thing like it's tslint-counterpart.

While tslint's no-void-expression tries to prevent users from assigning, returning or using the result of a void expression, eslint's no-void bans the void-keyword.

tslint's no-void-expression

tslint.json:

    "rules": {
        "no-void-expression": [
            true,
            "ignore-arrow-function-shorthand"
        ]
    }

Example of bad code for tslint's no-void-expression

tes.ts:

function test(): void { }
console.log(test()); // bad
let x = test(); // bad
function test2() { return test(); } // bad

Example for good code for tslint's no-void-expression

test.ts:

function test(): void { }
test(); // good

eslint's no-void

Example of bad code for eslint's no-void

function test(): void
{
    return void 0; // bad
}

Example of good code for eslint's no-void

function test(): void
{
    return undefined; // good
}

function test2(): void
{
    return; // good
}