Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error: non-defining opaque type use in defining scope #68

Closed
Ake-w opened this issue Oct 25, 2022 · 4 comments · Fixed by #73
Closed

error: non-defining opaque type use in defining scope #68

Ake-w opened this issue Oct 25, 2022 · 4 comments · Fixed by #73

Comments

@Ake-w
Copy link

Ake-w commented Oct 25, 2022

Bug Report

Version

volo v0.2.0

Platform

Windows 11 64-bit

active toolchain

nightly-x86_64-pc-windows-msvc (overridden by 'D:\volo-example\rust-toolchain.toml')
rustc 1.66.0-nightly (758f19645 2022-10-24)

Description

run this example

error: non-defining opaque type use in defining scope
   --> C:\Users\xxx\.cargo\registry\src\mirrors.ustc.edu.cn-61ef6e0cd06fb9b8\volo-0.2.0\src\loadbalance\random.rs:128:9
    |
128 | /         async {
129 | |             let key = discover.key(endpoint);
130 | |             let weighted_list = match self.router.entry(key) {
131 | |                 Entry::Occupied(e) => e.get().clone(),
...   |
148 | |             })
149 | |         }
    | |_________^ lifetime `'future` is part of concrete type but not used in parameter list of the `impl Trait` type alias
@storyseeker
Copy link

I encountered the same problem, how to solve it?

@PureWhiteWu
Copy link
Member

This is an issue of the rustc compiler: rust-lang/rust#100013
We are working on this, and will release a new version (perhaps) today.

@PureWhiteWu
Copy link
Member

Hello, version 0.2.1 is released, and this problem has been fixed.

@storyseeker
Copy link

Hello, version 0.2.1 is released, and this problem has been fixed.

It works. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants