David Delassus linkdd

See

I made a parser for a CSS dialect (with far less features) to style my C++ game UI (which is made with Clay).

Why? Well, plenty of reasons why not, so I'll just say:

The Letlang compiler translates the Letlang code to Rust code.

The structure is as follow:

	[package]
	name = "hurl-demo-stresstest-backend"
	version = "0.1.0"
	edition = "2024"

	[dependencies]
	anyhow = "1"
	tokio = { version = "1", features = ["full"] }
	hyper = { version = "1", features = ["full"] }
	hyper-util = { version = "0.1", features = ["full"] }

	let task_args: Vec<Value> = vec![];
	let mut block = func.call(&mut context, task_args);

	let ignored = Value::Boolean(bool::default());
	let mut state = block.resume_with(ignored);

	loop {
	match &state {
	GeneratorState::Yielded(FunctionInterruption::Effect { name, args }) => {
	// try to handle side effect

	tokio::spawn(async move {
	let process_handle = tokio::spawn(async move {
	// run process's function
	});

	let res = process_handle.await;
	// notify the node of the process termination
	});

	#[allow(unused_variables)]
	#[allow(unused_imports)]
	#[allow(dead_code)]

	mod symbol_a {
	use llcore_runtime::*;

	pub fn const_a(context: Arc<Mutex<Context>>) -> Value {
	Value::Primitive(PrimitiveValue::Number(42.0))
	}

	# Tooling configuration files
	FROM scratch AS context

	ADD package.json \
	yarn.lock \
	.eslintrc.js \
	.eslintignore \
	/workspace/

	# Source code