Exercise compiler fails on multiline string literals
See original GitHub issueIt appears the exercise compiler fails to parse multiline string literals. Ex:
/** multilineLiteralStrings
*
* Multiline String literals are surrounded by three quotation marks.
*/
def multilineLiteralStrings(res0: Int) {
val a =
"""An apple a day
keeps the doctor away"""
a.split('\n').size should be(res0) //a.split('\n').size determines the number of lines
}
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
multi-line string literals - Discussion - Swift Forums
I would very much like to implement multi-line string literals in swift and get ... a multi-line string in order to improve any...
Read more >C++ multi line string not working as expected - Stack Overflow
I've read on multiple threads and multiple websites that you can use the syntax R"(<string here>)"; or R"BANNER(<string here>)BANNER"; to ...
Read more >Multiline string literals should not be used - SonarSource Rules
Multiline string literals should not be used ... Continuing a string across a linebreak is supported in most script engines, but it is...
Read more >An idea for multiline strings : r/ProgrammingLanguages - Reddit
Introduction. So, I've been developing my language for quite some time and initially I went from having strings literals be. "{n}([^"\n]|\\.
Read more >Python Multi Line Strings - W3Schools
Note: in the result, the line breaks are inserted at the same position as in the code. Related Pages. Python Strings Tutorial String...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We can wait for it, we have other tickets to work on before official launch next Wednesday
@raulraja A fix is slated for Scala 2.11.9-- we can wait for it, or I can whip up a workaround. What do you think?