Using awaitable::Await causes invalid errors

General Issues and Bug Reporting
, , , ,
1

Summary

When using awaitable::Await() the Verse LSP will incorrectly flag it as an error.

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

  • Use awaitable::Await()
  • e.g. Interactable.SucceededEvent.Await()

Expected Result

The Verse LSP doesn’t flag it.

Observed Result

The Verse LSP flag an error.

Invalid access of internal function (/Verse.org/Verse/event:)Await from control scope

Unknown member Await in listenable(agent).

All the top level expressions in a 'race' macro must be async (such as a coroutine call) and not immediate.

Platform(s)

Version: 6.0.0-59596594 Branch: //Fortnite/Release-43.00

Island Code

N/A

2

FORT-1185403 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

3

Implicit super type conversions involving awaitables are also causing invalid errors:

Event: event() = event(){}

Awaitable()<computes> : awaitable() =
    Event # This function returns a value of type awaitable(true), but the function body's result is an incompatible value of type event(tuple()).  (3510)
4

Same, it’s pretty bad over here​:sob:
image

5

Hi all!

We have added this to our known issues, we’re investigating right now

6

Is there any update on this as I’m still getting this same error as well as this error:

image

*Update: The error in the image is because it doesn’t do the .Await properly so it’s linked.