distinction between re.replace and re.replacef; speed improvements for re module
This commit is contained in:
parent
e424e13bd9
commit
3005955d20
23 changed files with 206 additions and 171 deletions
9
todo.txt
9
todo.txt
|
|
@ -8,8 +8,6 @@
|
|||
- deprecate ^ and make it available as operator
|
||||
- test branch coverage
|
||||
- checked exceptions
|
||||
- do not ambiguity error for methods if ambiguity only affects the same
|
||||
dispatcher anyway
|
||||
- slicing
|
||||
|
||||
|
||||
|
|
@ -109,6 +107,13 @@ Version 2
|
|||
|
||||
type
|
||||
PWindow = ref TWindow not nil
|
||||
|
||||
The problem with ``nil`` is that the language currently relies on it for
|
||||
implicit initialization. Initialization is different from assignment. The
|
||||
issues can "easily" dealt with by ensuring:
|
||||
|
||||
var x = myProc() # checks myProc() initializes every pointer explicitely
|
||||
|
||||
- the two other parsers
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue