COLLECTED BY

Organization: Archive Team

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: Archive Team: The Github Hitrub

This collection is a set of Github repository archives from two major sets: A panic grab upon the acquisition by Microsoft, and a larger, ongoing set of Pretty Much Everything.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20201223155118/https://github.com/tinygo-org/tinygo/pull/1237

tinygo-org / tinygo

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

Jump to bottom

internal/task,transform: fix coroutines scheduling order #1237

Closed

niaow wants to merge 2 commits into tinygo-org:dev from niaow:coro-scheduling-order

Member

niaow commented Jul 12, 2020

This change applies a loop around resuming a task.
This means that a task will not suspend implicitly when returning from a function.

niaow added 2 commits


          internal/task,transform: fix coroutines scheduling order

33c9b69

This change applies a loop around resuming a task.
This means that a task will not suspend implicitly when returning from a function.


          tests/wasm: update channel test output for scheduling order change

2239ba7

aykevl reviewed

Member

aykevl left a comment

While the change itself seems fine, it does increase code size a little bit on WebAssembly. Therefore, I wonder why this is necessary? The Go specification does not define a particular order between goroutines unless explicit synchronization is used.

If this is for interrupts, I do not think this is a complete fix. I think interrupts are only really safe when used with the tasks scheduler as it is much easier to reason about ordering and heap allocation (no heap allocation on function calls, for example). The tasks scheduler should be implementable on any reasonable baremetal target.

src/internal/task/task_coroutine.go

  
        	*rawState

        	// retcon is set to true when a call returns and awakens it caller.

        	retcon bool

aykevl Jul 16, 2020
Member

What does `retcon` mean? "Return continue"?

Member Author

niaow commented Jul 16, 2020

I guess I will work on the coroutines replacement instead

niaow closed this

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

You can’t perform that action at this time.