Lîm Tsú-thuàn
Lîm Tsú-thuàn
NOTE: If I update existed execute signatures, will fail many tests and break API, so I will keep both versions for a while.
```c++ include/runtime/component/hostfunc.h --- C++ 107 107 108 108 template 109 109 static Tuple toTuple(SpanT &&Args, std::index_sequence) { 110 110 return Tuple(std::holds_alternative((Args)[Indices]) ... 111 ? std::get(std::forward(Args)[Indices]) 111 112 .template get() ......
Take note and mark as resolved. ### Problem 1 ```c++ template static Tuple toTuple(SpanT &&Args, std::index_sequence) { return Tuple(std::forward(Args)[Indices] .template get()...); } ``` cannot get proper handled after modification, even...
### Problem 2 Due to limitation of C++ function specialization, I cannot do below, I will try class template instead. ```c++ template inline ValType ValTypeFromType() noexcept { return InterfaceType( TypeCode::List,...
### Problem 3 If we consider the definition: ```c++ using ValInterface = std::variant; ``` There is a trouble: we would like to accept any `vector`/`span` as a variant of `ValInterface`,...
### Ubuntu/Debian ``` WasmEdge::RefVariant>>::__accepted_index' requested here using __accepted_type = __to_type; ^ /usr/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/variant:1405:24: note: in instantiation of template type alias '__accepted_type' requested here typename _Tj = __accepted_type, ^ /usr/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/variant:1409:2: note: in...
Even more crashed......
Next idea: still push_back, but use current `std::string` immediate construction.
@hydai Do we still want to fix manylinux2014?
By introducing `ValInterface` explicit, we fix build failed on each platform, which caused by ambiguous semantic when we do construction. 1. Alpine clang cannot decide `push_back` should use `T` of...