We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v -g run file.v
pub type Command = Assign | Call pub struct Assign {} pub struct Call { mut: text string } fn main() { mut command_arr_ptr := [ &Command(Call{}) ] mut command_arr_el_ptr := &command_arr_ptr[0] // type is && ? match mut command_arr_el_ptr { Call { //builder error: expected struct or union but not 'struct main__Command *' command_arr_el_ptr.text = "foo" } Assign { } } }
pub type Command = Assign | Call pub struct Assign {} pub struct Call { mut: text string } fn main() { mut command_arr_ptr := [ &Command(Call{}) ] mut command_arr_el_ptr := command_arr_ptr[0] println(typeof(command_arr_el_ptr)) // builder error: expected struct or union but not 'struct main__Command *' }
readable error or ok
builder error
No response
V 0.4.9 6d017f3
Note
You can use the 👍 reaction to increase the issue's priority for developers.
Please note that only the 👍 reaction to the issue itself counts as a vote. Other reactions and those to comments will not be taken into account.
The text was updated successfully, but these errors were encountered:
Connected to Huly®: V_0.6-22187
Sorry, something went wrong.
No branches or pull requests
Describe the bug
v -g run file.v
Reproduction Steps
Expected Behavior
readable error or ok
Current Behavior
builder error
Possible Solution
No response
Additional Information/Context
No response
V version
V 0.4.9 6d017f3
Environment details (OS name and version, etc.)
Note
You can use the 👍 reaction to increase the issue's priority for developers.
Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.
The text was updated successfully, but these errors were encountered: