-
could this be simplified to an `enum Broker { Ip, Named }` instead of having the trait and type param propagation through the stack?
The two issues are:
* the resolver type/`Dns` trait: where the …
-
### Context
A contract calls another contract to return a struct.
This results in an error message indicating that `AbiDecode` trait must be implemented.
Upon implementing a template `AbiDecode` …
-
### Is your feature request related to a problem? Please describe.
I am always frustrated when I fight something in melee combat and don't die incredibly quickly, and also when I am able to just go t…
-
I'm working on a modpack, and id like maces and both hammers to penetrate armor, and id like most 2 handed weapons to have the parrying daggers block. Is there any way to change the traits? Sorry if t…
-
*Disclaimer:* Hi guys, I'm relative new to TON ecosystem but AFAIK there's no standardized approach for upgradable contracts in Tact.
### Motivation
Motivation for this issue is to discuss some ap…
-
### Goal
To support additional use cases, such as evaluating identities in different contexts or managing anonymous identities, we aim to enable our SDK users to:
1. Evaluate flags against ident…
-
For discussion.
## Trait data issues
**Exclude term matches in references, citations, taxon names**
Many invalid trait data records seem to come from term matches in references or citations o…
-
The following compiles:
```rust
#![feature(trait_upcasting)]
trait Super {}
trait Trait: Super {}
fn foo(x: &dyn Trait) -> &dyn Super { x }
```
while this does not:
```rust
#![feature(trait…
-
On vscode im using default them like this one
i've added some customization that allows me
to clearly distinguished different types
Vscode settings snippet
```json
"editor.tokenColorCustom…
-
Following up to #4202 and #4206 I wanted to write down something I've been thinking about for a while. It looks like we're moving ahead with accepting those options so I'll assume that at least the de…