JC
JC
Previously on Sway, we have introduced `raw_ptr` and `raw_slice` types as better alternatives to using `u64` and `(u64,u64)`. While we eventually wanted to get rid of these types, they helped...
- [ ] Tests are failing. Fix parsing of `__ptr[T]` and `__slice[T]`. - [ ] Replicate `raw_ptr` and `raw_slice` tests for the typed variants. - [ ] Contact the SDK...
Interface and Contract should have support for accessing storage slots. Blockers - [x] Storage API/syntax needs to be decided
Currently we have at least two files that cause issues when the repo is cloned in a case-insensitive environment: `_data/icons/LaChain.json` `_data/icons/lachain.json` It would be cool if we fixed these issues...
There's a whole lot of Windows developers out there who would love to use this too, and who will contribute based on it.
I jumped in to fix the problem i stated in https://github.com/montagejs/collections/issues/132, but even with `[email protected]` the tests fail: ``` $ npm test > [email protected] test /Users/user/gtor > jasminum test /Users/user/gtor/test/behavior-test.js...
I think it would be great if the syntax was closer to what's being introduced in [Import Assertions](https://github.com/tc39/proposal-import-assertions): ```ts import logoModuleReference from "./logo.svg" as reference; // OR const logoModuleReference: ModuleReference...
Should these work? ```javascript // Example 1 asset reactRef from 'react'; import React, { Component } from reactRef; // Example 2 import { reactRef } from './myRefs'; import React, {...
When working on a JS project, sourcing deps like forc and fuel-core is an issue. To make this easier, we can follow the example of other non-JS projects that want...