ParserBase could be optimized
@ezio-melotti ya está trabajando en esto.
Desde el 1/5/2022.
- Lenguaje dominante
- Python
- Estrellas
- 77.2k
- Forks
- 36k
- Métricas de merge de PR
- Métricas de PR pendientes
Descripción
There is a lot of wasteful CPU code in this fashion (seen multiple times) :-
if ")" in rawdata[j:]:
j = rawdata.find(")", j) + 1
search performed in string twice, even if we could just do it once.
Consider the strings immutable, then on every slice a new string is created on the fly.
Moreover, the slicing done at rawdata[j:], is bound to be quite expensive depending on the size of the string.
We could eliminate slicing altogether and only have one find operation in this style :-
RPAREN_pos = rawdata.find(")", j)
if find_RPAREN != -1:
j = RPAREN_pos + 1
I'm new to Open Source Code Contributions. Would love to learn from other's coding style & know other's point of view.
Originally posted by @be-thomas in https://github.com/python/cpython/issues/92084#issuecomment-1114023102
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.