Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

295
Views
¿Por qué no se puede llamar a esta expresión, si solo se inicializa en una Promesa?
let callback1: null | (() => void) = () => {}; let callback2: null | (() => void) = null; let callback3: null | (() => void) = null; if (callback1 != null) callback1(); // callable callback2 = () => {} if (callback2 != null) callback2(); // callable new Promise<void>(() => callback3 = () => {}); if (callback3 != null) callback3(); // not callable // ^^^ // This expression is not callable. // Type 'never' has no call signatures.

Patio de juegos

Parece que TypeScript está haciendo un análisis estático, pero de forma incorrecta, ya que el código funciona bien en JS:

 let callback3 = null; new Promise(() => callback3 = () => { console.log("It Works"); }); if (callback3 != null) callback3(); // output: It Works
about 4 years ago · Santiago Gelvez
1 answers
Answer question

0

Dado que inicia callback3 con un null literal y no lo modifica, TS infiere su tipo como null .

con if (callback3 != null) lo está reduciendo para que never se produzca el error.

Esto no sucede en este tipo de caso:

 declare const maybeCallback: null | (() => void); callback3 = maybeCallback; if(callback3 !== null) { // () => void not never }

Patio de juegos

about 4 years ago · Santiago Gelvez Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!