From 3f217b3ed61f3ddd4fd49dfbb330d43aa2a96de4 Mon Sep 17 00:00:00 2001 From: Arseny Kapoulkine Date: Mon, 17 May 2021 16:39:39 -0700 Subject: [PATCH] Update syntax-method-call-on-string-literals.md Clean up highlighting --- rfcs/syntax-method-call-on-string-literals.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rfcs/syntax-method-call-on-string-literals.md b/rfcs/syntax-method-call-on-string-literals.md index 6e2f9732..877774d0 100644 --- a/rfcs/syntax-method-call-on-string-literals.md +++ b/rfcs/syntax-method-call-on-string-literals.md @@ -33,7 +33,7 @@ By itself, this change introduces an additional ambiguity because of the combina Consider code like this: -``` +```lua local foo = bar ("fmt"):format(...) ``` @@ -46,7 +46,7 @@ The grammar today also allows calling functions with string literals as their fi By itself, this proposal thus would create a similar ambiguity in code like this: -``` +```lua local foo = bar "fmt":format(...) ``` @@ -55,7 +55,7 @@ While we could extend the line-based error check to include function literal arg Doing so would prohibit code like this: -``` +```lua "fmt":format(...) ```