Script# 和 System.IO.Stream
我目前正在努力获取 7-Zip 压缩库的 C# 源代码以在 Script# 上进行编译，但面临 Script# 版本的 BCL 不支持 System.IO.Stream 的问题。有什么建议如何处理这个问题吗？
I'm currently working on getting the C# Source for the 7-Zip compression library to compile on Script# but facing the problem that System.IO.Stream is not supported in Script#'s version of the BCL. Any suggestions how to handle this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
理论上，您可以定义一个 Stream 并在与字节对应的数字数组上实现 - 然而，脚本在处理字节序列方面并不是那么好（直到我们在脚本中获得类型数组）。
流在脚本代码中并不常用 - 通常您有一个文本响应，例如来自 XHR 请求的文本响应，或者来自画布元素的图像数据的 Base64 编码字符串（在某些典型情况下您可能需要流）。因此它们并不是开箱即用的。
如果您确实定义了一个，也许您可以分享您的工作。如果您认为您拥有的 7-zip 压缩足够通用，并且可以公开共享，那么很乐意进一步讨论。如您所知，script# 位于 github 上，看到社区贡献和扩展的生态系统将会很有趣。
You could theoretically define a Stream and implement on your end over an array of numbers corresponding to the bytes - script isn't all that great at dealing with byte sequences however (until we get typed arrays in script).
Streams aren't that commonly used within script code - typically you have a text response for example from an XHR request, or a base64-encoded string for image data from a canvas element (some typical cases where you might have expected streams). Hence they're not there out-of-the-box.
If you do define one, perhaps you can share your work. If you think the 7-zip compression you have is general purpose enough, and publicly shareable, would love to discuss further. As you hopefully know, script# is on github, and would be interesting to see an ecosystem of community contributions and extensions.