Feature: `__` private members/name mangling in classes

Abierto
#853 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
javascript, python
Área
compilers

Línea de trabajo

Start by reviewing the linked Python documentation on private variables and name mangling, then inspect how Transcrypt currently handles class members and mixins. No source files, tests, or entry points are named in the issue. Done would require an agreed implementation scope and tests demonstrating the expected mangling behavior in generated JavaScript.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

IS: enhancement IS: exploratory

Sorry, I would expect that this probably documented but I just cannot find it:

https://docs.python.org/3/tutorial/classes.html?highlight=name%20mangling#private-variables

Short question: Is this supported in some way? Or are there plans to support it?

It seems to be such a core-feature of Python that I kind of feel stupid to ask, I would bet that it was decided to not implement that feature somewhere/somehow, but I cannot find a reference to that decision or if it even was made?

To me this would be a very awesome feature, because it is for me the feature that avoids naming collisions in classes for something like Class-Mixins. I am reviving an old project of mine which consists converting an old piece of Python code to a web-capable implementation, and this would make those conversion efforts a LOT more convenient.

Lenguaje dominante
Python
Estrellas
2.9k
Forks
218
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TranscryptOrg/Transcrypt

Todos los issues de TranscryptOrg/Transcrypt

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.