lambda doesn't work as struct field

[islonely]

Describe the bug

Can't use lambda as struct field.

Reproduction Steps

module main

import cli
import os

const (
	no_args = '
Usage: cssml [options] <file>

Options:
	-h, --help     output usage information
	-v, --version  output the version number'
)

fn main() {
	mut app := cli.Command{
		name: 'cssml',
		description: 'A CSSML compiler - CSS and HTML in one file.',
		execute: |cmd| println(no_args)
	}
	app.setup()
	app.parse(os.args)
}

Expected Behavior

Expected code to compile and print the no_args const when executed without cli arguments.

Current Behavior

error: invalid expression: unexpected token `|`

Possible Solution

No response

Additional Information/Context

I have a fix for this, but it will allow lambdas anywhere an anonymous function is expected.

V version

V 0.4.1 a685088

Environment details (OS name and version, etc.)

v full version: V 0.4.1 a685088
Os: linux, Ubuntu 20.04.6 LTS (VM)
Processor•
8 cpus, 64bit, little endian, AMD EPYC 7763 64-Core Processor
getwd: /workspaces/assmi vexe: /opt/v/v
vexe mime: 2023-09-23 23:29:02
vroot: OK, value: /opt/v
MODULES: OK, value: /home/codespace/.vmodules
VTMP: OK, value: /tmp/v 1000
Git version: git version 2.41.0
Git vroot status: weeklv.2023.33-210-aa685088€ .git/config present: true
CC version: cC (Ubuntu 9.4.0-lubuntul~20.04.1) 9.4.0
thirdparty/tcc status: thirdparty-linux-amd64 12£392c3

Important

You can vote for this issue using the 👍 reaction. More votes increase the issue's priority
for developers.

Take into account that only the 👍 reaction counts as a vote.
Only reactions to the issue itself will be counted as votes, not comments.

[islonely]

After looking into the compiler to try and fix myself: This is caused by the parser (and checker once parser check is removed) not allowing lambdas as values outside of function args. Kinda makes sense I suppose, but on the other hand it doesn't make sense that they aren't allowed anywhere an anonymous function type is already declared. In that case, this is technically not a bug (compiler's doing what it's supposed to do).

[islonely]

This code already exists to block lambdas from just be assigned to values where they shouldn't belong. var := |x,y| x+y would not be allowed, but var = |x,y| x+y would be if mut var := fn(x int, y int) int { return x+y } was declared earlier. Also fixes, the issue mentioned in the original post of struct field values not working.

if exp_sym.kind != .function {
	c.error('a lambda expression was used, but `${exp_sym.kind}` was expected', node.pos)
	return ast.void_type
}