Why not generating === instead of == ?

Open
#641 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript, python
Domain
compilers

Research direction

Start by tracing how Python equality and inequality comparisons are lowered into generated JavaScript. Check the existing compiler tests for comparison behavior, then determine whether strict operators preserve the relevant Python semantics and add coverage showing the intended generated output and runtime behavior.

Written by the indexing model from the issue text.

Description

IS: bug STATE: under consideration

I have noticed that for comparisons transrypt generates == operators, which in JavaScript can try to coerce types wherever necessary and "1" == 1, while in python this is not the case. Why not generating === from python == and !== from python != ? This would make generated code behave closer to python and will help to avoid bugs.

Dominant language
Python
Stars
2.9k
Forks
218
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TranscryptOrg/Transcrypt

All issues in TranscryptOrg/Transcrypt

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.