Comments (2)
I'm not really pleased with the _raw
suffix to make a distinction between YAML representation (return
, arguments
) using YAML objects and string representation (return_raw
, 'arguments_raw') using the abstract or specific programming language. Can't think of a good alternative for now that indicates "code fragment expressed in abstract/specific programming language".
If we would manage to extend the YAML parser so that (only) TESTed data types can be used as !!
-types, we could also create a special (non-TESTed) type raw
(sticking to that name for now) that would allow to write return: !!raw 'string'
as an alternative for return_raw: 'string'
. Maybe we don't even want the return_raw
attribute anymore if this would be possible.
from universal-judge.
Even better: the only time where a unified return
may not explicitly differentiate between YAML representation and string representation is when its value is a string. The default interpretation of such a string could be as the string representation. As such, return
, expression
and statement
all have string representations as values. To interpret as a string as a literal string in YAML representation, we could use an explicit !!string
cast.
Same strategy could also be applied to arguments
, where each string argument would need its own !!string
cast if all are given in YAML representation.
from universal-judge.
Related Issues (20)
- JSON failed to parse HOT 1
- Fetch stdin from file as an alternative to inlining it into test suite HOT 1
- Do not quote options on bash command lines generated by TESTed
- Support tests for files
- Generate "final" variables if possible
- Show stdin as a separate channel when used in combination with arguments HOT 2
- Closing newline insertion HOT 1
- Specify interface that must be implemented
- Link bash compilation error to corresponding line in code
- Support before/after in DSL
- Support attribute assignment
- Testing stdin/stdout and expressions at the same time? HOT 3
- Update node.js to latest version HOT 3
- JavaScript: consider alternative ways to create object as alternatives HOT 1
- Bug with Javascript objects
- representation of Set and Map as return value HOT 3
- Add some extra tests for the set/map type restrictions
- Bump JavaScript exercises repo commit in tests
- Dodona features for language-agnostic exercices
- Measure/estimate complexity (time and memory) HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from universal-judge.