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
The general consensus in semantic versioning is that patch releases should not contain breaking changes.
The 0.2.2 release deprecated a field and this introduced breaking changes, at least in the wit-bindgen + C APIs
/usr/local/lib/wasi-sdk-22.0/bin/clang -c wasi_http.c -o wasi_http.o wasi_http.c:48:5: error: unknown type name 'client_tuple2_field_key_field_value_t'; did you mean 'client_tuple2_field_name_field_value_t'? 48 | client_tuple2_field_key_field_value_t *headers = malloc(sizeof(client_tuple2_field_key_field_value_t) * wasi_response.headers.len); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | client_tuple2_field_name_field_value_t ./client.h:418:3: note: 'client_tuple2_field_name_field_value_t' declared here 418 | } client_tuple2_field_name_field_value_t; | ^ wasi_http.c:48:68: error: use of undeclared identifier 'client_tuple2_field_key_field_value_t' 48 | client_tuple2_field_key_field_value_t *headers = malloc(sizeof(client_tuple2_field_key_field_value_t) * wasi_response.headers.len); | ^ wasi_http.c:56:5: error: unknown type name 'client_list_tuple2_field_key_field_value_t'; did you mean 'client_list_tuple2_field_name_field_value_t'? 56 | client_list_tuple2_field_key_field_value_t header_list = { | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | client_list_tuple2_field_name_field_value_t ./client.h:423:3: note: 'client_list_tuple2_field_name_field_value_t' declared here 423 | } client_list_tuple2_field_name_field_value_t; | ^ wasi_http.c:106:5: error: unknown type name 'client_tuple2_field_key_field_value_t'; did you mean 'client_tuple2_field_name_field_value_t'? 106 | client_tuple2_field_key_field_value_t content_type[] = {{ | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | client_tuple2_field_name_field_value_t ./client.h:418:3: note: 'client_tuple2_field_name_field_value_t' declared here 418 | } client_tuple2_field_name_field_value_t; | ^ wasi_http.c:114:5: error: unknown type name 'client_list_tuple2_field_key_field_value_t'; did you mean 'client_list_tuple2_field_name_field_value_t'? 114 | client_list_tuple2_field_key_field_value_t headers_list = { | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | client_list_tuple2_field_name_field_value_t ./client.h:423:3: note: 'client_list_tuple2_field_name_field_value_t' declared here 423 | } client_list_tuple2_field_name_field_value_t; | ^ wasi_http.c:194:5: error: unknown type name 'client_list_tuple2_field_key_field_value_t'; did you mean 'client_list_tuple2_field_name_field_value_t'? 194 | client_list_tuple2_field_key_field_value_t header_list; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | client_list_tuple2_field_name_field_value_t ./client.h:423:3: note: 'client_list_tuple2_field_name_field_value_t' declared here 423 | } client_list_tuple2_field_name_field_value_t; | ^ 6 errors generated. make: *** [Makefile:17: wasi_http.o] Error 1
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The general consensus in semantic versioning is that patch releases should not contain breaking changes.
The 0.2.2 release deprecated a field and this introduced breaking changes, at least in the wit-bindgen + C APIs
The text was updated successfully, but these errors were encountered: