fzyzcjy / flutter_rust_bridge

Flutter/Dart <-> Rust binding generator, feature-rich, but seamless and simple.
https://fzyzcjy.github.io/flutter_rust_bridge/
MIT License
4.27k stars 300 forks source link

Run Dart build_runner never finishes running (internal loop?) #2097

Closed Larpoux closed 5 months ago

Larpoux commented 5 months ago

Describe the bug

when I code this :

use flutter_rust_bridge::frb;
use web_audio_api::node::AudioNode as XAudioNode;
pub trait AudioNode
{
        #[frb(sync)]
        fn get_x_node(&self) -> &dyn web_audio_api::node::AudioNode ;

        #[frb(sync)]
        fn connect(&self, dest:&dyn AudioNode) ->&dyn AudioNode
        {
                let toto = self.get_x_node();
                let titi = dest.get_x_node();
                toto.connect(titi);
                dest
        }
}

FRB enters an infinite internal loop (never finishes).

toto.log

Steps to reproduce

-

Logs

See attachment

Expected behavior

No response

Generated binding code

-

OS

No response

Version of flutter_rust_bridge_codegen

flutter_rust_bridge_codegen 2.0.0-dev.40

Flutter info

No response

Version of clang++

No response

Additional context

No response

fzyzcjy commented 4 months ago

Wow great, happy to hear that!

the .dart_tool directory.

The thing is that

Larpoux commented 4 months ago

@fzyzcjy : you did a tremendous work. This is really amazing. Well done. 🥇

I just hope that you will continue to improve frb. My wish is to offer a complete W3C Web Audio API to the flutter users and not a subset of the recommendation.

fzyzcjy commented 4 months ago

I just hope that you will continue to improve frb. My wish is to offer a complete W3C Web Audio API to the flutter users and not a subset of the recommendation.

Sure! Currently it is already a large subset, but I will try to find some time working on the rest.

github-actions[bot] commented 4 months ago

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new issue.