Data

Tools

Indexes

Applications

Experiments

Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / WebAssembly/stringref issues and pull requests

#67 - is this proposal dead?

Issue - State: open - Opened by pannous about 1 year ago

#65 - Clarity on units of string

Issue - State: open - Opened by Maxdamantus over 2 years ago - 16 comments

#64 - Stringref as a toolchain concept

Issue - State: open - Opened by wingo over 2 years ago - 3 comments

#63 - Substrings: slices vs. copies

Issue - State: open - Opened by jakobkummerow over 2 years ago - 1 comment

#62 - Langues where strings are primarily UTF-8

Issue - State: open - Opened by eqrion over 2 years ago - 19 comments

#61 - Update code unit definition in Overview.md

Pull Request - State: open - Opened by dcodeIO almost 3 years ago

#60 - New instruction `string.hash`

Issue - State: open - Opened by Liedtke about 3 years ago - 5 comments

#59 - New instruction `string.from_code_point`

Issue - State: open - Opened by Liedtke about 3 years ago - 7 comments

#58 - New three-way string comparison instruction similar to `std::strcmp` in C++

Issue - State: open - Opened by Liedtke about 3 years ago - 4 comments

#57 - Performance report for kotlin wasm compiler

Issue - State: open - Opened by igoriakovlev about 3 years ago - 3 comments

#56 - Algorithmic complexity of instructions

Issue - State: open - Opened by eqrion about 3 years ago - 2 comments

#55 - string.new_lossy_utf8

Issue - State: open - Opened by annevk about 3 years ago - 1 comment

#54 - No new string implementations on the web: allow re-use of JS engine's strings

Issue - State: open - Opened by annevk about 3 years ago - 13 comments

#52 - Does the interpreter support `stringref` yet?

Issue - State: closed - Opened by yviansu over 3 years ago - 2 comments

#51 - Possible addition: number-to-string conversions

Issue - State: open - Opened by jakobkummerow over 3 years ago

#50 - Fallible UTF-8 decoding?

Issue - State: open - Opened by askeksa-google over 3 years ago - 2 comments

#49 - stirng.encode_wtf16_array with start/end

Issue - State: open - Opened by gkdn over 3 years ago - 3 comments

#48 - stringref instructions operands and results have non-nullable type

Pull Request - State: open - Opened by wingo over 3 years ago

#47 - stringref should be non-nullable by default?

Issue - State: open - Opened by wingo over 3 years ago - 4 comments

#46 - Fold WTF-8 policy into instructions

Pull Request - State: closed - Opened by wingo over 3 years ago

#45 - Binary encoding of opcodes after 0xfb prefix are LEBs

Pull Request - State: closed - Opened by wingo over 3 years ago

#44 - It should be possible to get a string from a stringview

Issue - State: open - Opened by wingo over 3 years ago - 1 comment

#43 - Consider changing entry points for string creations, return types and their names

Issue - State: open - Opened by gkdn over 3 years ago - 8 comments

#41 - Shift type opcodes

Issue - State: open - Opened by rossberg over 3 years ago - 1 comment

#40 - Stringref should probably be a subtype of anyref

Issue - State: open - Opened by wingo over 3 years ago - 13 comments

#39 - Can encoding instructions use memory as a scratch space?

Issue - State: open - Opened by wingo over 3 years ago - 2 comments

#37 - [Feature] string.ord or string.lt + string.gt

Issue - State: open - Opened by MaxGraey over 3 years ago - 4 comments

#36 - stringview_wtf16.encode returns number of written code units

Pull Request - State: closed - Opened by wingo over 3 years ago

#35 - Policy immediates

Issue - State: closed - Opened by kripken over 3 years ago - 1 comment

#34 - Perhaps allow substrings in string literal section

Issue - State: open - Opened by wingo over 3 years ago - 2 comments

#33 - string.encode_wtf8, string.encode_wtf16 return encoded length

Pull Request - State: closed - Opened by wingo over 3 years ago

#32 - Allow null operands to string.eq

Pull Request - State: closed - Opened by wingo over 3 years ago

#31 - String slice operands have exclusive end

Pull Request - State: closed - Opened by wingo over 3 years ago

#30 - Further WTF-16 byte order clarification

Pull Request - State: closed - Opened by wingo over 3 years ago

#29 - Change stringview_iter.cur to stringview_iter.next

Pull Request - State: closed - Opened by wingo over 3 years ago

#28 - Integrate with GC proposal

Pull Request - State: closed - Opened by wingo over 3 years ago - 2 comments

#27 - String literal section text format

Issue - State: open - Opened by dcodeIO over 3 years ago

#26 - Clarify string literal requirement

Pull Request - State: closed - Opened by dcodeIO over 3 years ago - 1 comment

#25 - Clarify string literal section kind

Pull Request - State: closed - Opened by dcodeIO over 3 years ago - 1 comment

#23 - Spec to-do: text format

Issue - State: open - Opened by wingo over 3 years ago

#22 - Make wtf-8 and wtf-16 handling more uniform

Pull Request - State: closed - Opened by wingo over 3 years ago

#21 - `string.new_wtf8` versus invalid byte sequences

Issue - State: closed - Opened by wingo over 3 years ago - 1 comment

#20 - Is stringref a subtype of eqref?

Issue - State: open - Opened by eqrion over 3 years ago - 20 comments

#19 - Clamping versus trapping for invalid offsets

Issue - State: open - Opened by wingo over 3 years ago - 2 comments

#18 - Behavior of string.eq for null strings

Issue - State: closed - Opened by wingo over 3 years ago - 3 comments

#17 - String slice operands should have exclusive end

Issue - State: closed - Opened by wingo over 3 years ago

#16 - Fix ordering between memory writes and effects

Issue - State: open - Opened by wingo almost 4 years ago - 10 comments

#15 - Does string.new_wtf16 use LE or BE encoding?

Issue - State: closed - Opened by eqrion almost 4 years ago - 1 comment

#14 - stringref default value: empty instead of null?

Issue - State: closed - Opened by carlopi almost 4 years ago - 4 comments

#13 - Define JS API

Issue - State: open - Opened by wingo almost 4 years ago - 4 comments

#12 - Is there a better name for `stringview_wtf16`

Issue - State: open - Opened by wingo almost 4 years ago - 11 comments

#11 - Binary format: consider deferring some string literals until after code section

Issue - State: open - Opened by wingo almost 4 years ago - 6 comments

#10 - Add binary encoding

Pull Request - State: closed - Opened by wingo almost 4 years ago - 1 comment

#9 - Decide on binary encoding

Issue - State: closed - Opened by wingo almost 4 years ago - 16 comments

#8 - Alternative: Library API

Issue - State: open - Opened by wingo almost 4 years ago

#7 - Is `stringview_wtf8` useful enough and fit for purpose?

Issue - State: open - Opened by wingo almost 4 years ago

#6 - Does `string.is_usv_sequence` pull its weight?

Issue - State: open - Opened by wingo almost 4 years ago - 3 comments

#5 - Library functionality: toUpperCase, etc

Issue - State: open - Opened by wingo almost 4 years ago - 11 comments

#4 - Replace `stringview_iter.cur` with `stringview_iter.next`

Issue - State: closed - Opened by wingo almost 4 years ago

#3 - Subtyping relationship between stringref and stringviews

Issue - State: open - Opened by wingo almost 4 years ago - 1 comment

#2 - Require valid UTF-8 string literals?

Issue - State: open - Opened by wingo almost 4 years ago - 4 comments

#1 - Integrate with GC proposal

Issue - State: closed - Opened by wingo almost 4 years ago - 2 comments