As a Go developer, I've had enough of Go's current syntax. I really like your approach, but I have a suggestion.
I believe that if this project wants to attract Go developers, it should use mainstream Go syntax instead of making extensive modifications. Otherwise, it will drastically increase the mental burden on Go developers, hindering its promotion and appeal.
Some examples:
keywork: fn -> func
code block: task {} -> go func() {}
generics: let (tx, rx) = Channel.new<string>().split() -> tx, rx := Channel.new[string]().split()
from your code example in readme
As a Go developer, I've had enough of Go's current syntax. I really like your approach, but I have a suggestion.
I believe that if this project wants to attract Go developers, it should use mainstream Go syntax instead of making extensive modifications. Otherwise, it will drastically increase the mental burden on Go developers, hindering its promotion and appeal.
Some examples:
keywork:
fn -> funccode block:
task {} -> go func() {}generics:
let (tx, rx) = Channel.new<string>().split() -> tx, rx := Channel.new[string]().split()from your code example in readme