feat: replace new keyword with this constructor syntax and ClassName.new() calls across core library and docs
Replace all uses of the `new` reserved word with explicit `this new()` constructor definitions and `ClassName.new()` instantiation calls in builtin/core.wren. Update all documentation files (classes.markdown, fiber.markdown, fn.markdown, sequence.markdown, error-handling.markdown, expressions.markdown, fibers.markdown, functions.markdown) to reflect the new constructor syntax, removing `new` keyword examples and replacing them with `ClassName.new()` patterns and `this new()` definitions.
This commit is contained in:
+4
-3
@@ -148,14 +148,15 @@ class Test:
|
||||
|
||||
|
||||
def validate_runtime_error(self, error_lines):
|
||||
if not error_lines:
|
||||
if len(error_lines) < 2:
|
||||
self.fail('Expected runtime error "{0} and got none.',
|
||||
runtime_error_message)
|
||||
self.runtime_error_message)
|
||||
return
|
||||
|
||||
# Make sure we got the right error.
|
||||
if error_lines[0] != self.runtime_error_message:
|
||||
self.fail('Expected runtime error "{0}" and got:', runtime_error_message)
|
||||
self.fail('Expected runtime error "{0}" and got:',
|
||||
self.runtime_error_message)
|
||||
self.fail(error_lines[0])
|
||||
|
||||
# Make sure the stack trace has the right line.
|
||||
|
||||
Reference in New Issue
Block a user