Const variable in quantum state after error in assigment function call

[DiogoJunqueiraGeraldo]

• Version: v12.18.4.
• Platform: Darwin MacInBoxs-MacBook-Pro.local 19.5.0 Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64 x86_64
• Subsystem: Unkown

What steps will reproduce the bug?

In node console execute:

// Assigment function who will throw the error 
function throwError() {
    throw new Error();
}

// throws an error as expected (can't create a const variable without value)
const foo; 

// functions throws an error as expected
const foo = throwError(); 

// Throws an ReferenceError of variable not defined
foo; 

// Throws an TypeError of Assigment to const variable
foo = 1; 

How often does it reproduce? Is there a required condition?

Always there is an error while assigning to a const variable

What is the expected behavior?

Not create the const variable

What do you see instead?

Const variable created without value

Additional information

[devsnek]

Duplicate of #8309