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

Meeting 11th May 2020 #1941

Closed
7 tasks done
fubuloubu opened this issue Apr 27, 2020 · 7 comments
Closed
7 tasks done

Meeting 11th May 2020 #1941

fubuloubu opened this issue Apr 27, 2020 · 7 comments
Labels
meeting Meeting

Comments

@fubuloubu
Copy link
Member

fubuloubu commented Apr 27, 2020

Start time: 18:00 UTC (https://time.is/UTC)

Vidchat link: https://meet.google.com/nvw-nvzt-zrs

Agenda:

@fubuloubu fubuloubu mentioned this issue Apr 27, 2020
7 tasks
@fubuloubu fubuloubu pinned this issue Apr 27, 2020
@fubuloubu fubuloubu changed the title Meeting 4th May 2020 Meeting 11th May 2020 May 4, 2020
@sbellem
Copy link
Contributor

sbellem commented May 4, 2020

Hi,

is the meeting open to "outsiders"? I am asking because I am curious about the roadmap of the project and perhaps I could help a bit.

Thanks,
Sylvain

@fubuloubu
Copy link
Member Author

@sbellem yes, it is open! We try to have the meeting on time, but sometimes we end up missing it, so just keep an eye on gitter and this issue around the time it is scheduled to start for updates on date/time and vidchat links. You are free to listen, join in the discussion, or propose topics to discuss in the agenda here!

@sbellem
Copy link
Contributor

sbellem commented May 5, 2020

Thanks @fubuloubu!

@fubuloubu
Copy link
Member Author

Call in 45 mins!

@rayrrr
Copy link

rayrrr commented May 12, 2020

Sorry I missed the meeting, busy day at work. Was it recorded by chance? Wondering on any outcomes related to #1440

@fubuloubu
Copy link
Member Author

fubuloubu commented May 12, 2020

@rayrrr we usally don't record the meetings, they're fairly low-key, but we feed back all decisions to GitHub.

On #1440, @iamdefinitelyahuman and I bikeshedded for 20 mins and we feel like we finally arrived at a good specification. It's only a mild bastardization of the Python slice syntax, but it effectively makes a delineation between static and dynamic arrays. Probably the first step towards implementing it will be to extend bytes[N] and string[N] by adding the calldata min-max length check, and require the new syntax of Bytes[M:N] and String[M:N] (which is a breaking change).

This will hopefully implement most of the functionality in the metaclasses that will support the more general Array[type, M:N] syntax, where type can be any type with a statically known size (at compile time). We might do this in stages, starting with basic types first, but this is currently the number 1 most-requested feature on our list for the 0.2.x-series (followed closely by abi_decode)

@fubuloubu fubuloubu added the meeting Meeting label May 12, 2020
@fubuloubu
Copy link
Member Author

Next: #1965

@fubuloubu fubuloubu unpinned this issue May 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meeting Meeting
Projects
None yet
Development

No branches or pull requests

3 participants