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

Visit Asynchronous and Synchronous method calls #41

Open
vlad-serbanescu opened this issue Jul 28, 2015 · 3 comments
Open

Visit Asynchronous and Synchronous method calls #41

vlad-serbanescu opened this issue Jul 28, 2015 · 3 comments

Comments

@vlad-serbanescu
Copy link
Contributor

No description provided.

vlad-serbanescu pushed a commit that referenced this issue Jul 28, 2015
@nobeh
Copy link
Member

nobeh commented Jul 28, 2015

I think if we still have a failing test, that's also good. This means we can have it under radar until the grammar is fixed/updated.

@bezirg
Copy link
Contributor

bezirg commented Jul 29, 2015

Hi Vlad and Behrooz, as I told you in the mailing list, the simplest way to fix the grammar is to simple remove (comment out) the two thissynchronous and thisasynchronous method calls.

@nobeh
Copy link
Member

nobeh commented Jul 29, 2015

Just referencing 414e42c to make a link for future.

nobeh added a commit that referenced this issue Jul 29, 2015
- Apply a few refactorings
- Note that IPrime.abs is not yet a purely valid ABS program
- MapReduce.abs a lot of issues yet to support; so ignored

Rel #41
@nobeh nobeh modified the milestones: 0.5.0, 1.0.0 Jul 29, 2015
nobeh added a commit that referenced this issue Jul 29, 2015
- Cache method signatures and variable declarations.
- Fetch method return types in an eager, find-first way.

Rel #41
nobeh added a commit that referenced this issue Aug 3, 2015
vlad-serbanescu pushed a commit that referenced this issue Aug 4, 2015
- introduced await argument in visitAsyncMethodCall to differentiate
between send and await ABS-API functions.
- introduced ALREADY_DEFINED constant to differentiate between
assignments of method calls and initializtions with method calls.
ALREADY_DEFINED DOES NOT affect initilizations.
- ALREADY_DEFINED has 2 small side effects:
*when constructing a Callable for an assignment of variable or class
field to asyncCall , the generic type is ?
*when constructing a Callable for an assignment of variable to sync
call, generic type is ?
vlad-serbanescu pushed a commit that referenced this issue Aug 4, 2015
Added this to FieldGuard visit
vlad-serbanescu added a commit that referenced this issue Aug 5, 2015
- fixed <?> side effect
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants