Search · sealed

GitHub’s search supports a variety of different operations. Here’s a quick cheat sheet for some of the common searches.

For more information, visit our search help section.

Basic search

This search	Finds repositories with…
cat stars:>100	Find cat repositories with greater than 100 stars.
user:defunkt	Get all repositories from the user defunkt.
tom location:"San Francisco, CA"	Find all tom users in "San Francisco, CA".
join extension:coffee	Find all instances of join in code with coffee extension.
NOT cat	Excludes all results containing cat.

Repository search looks through the projects you have access to on GitHub. You can also filter the results:

This search	Finds repositories with…
cat stars:>100	Find cat repositories with greater than 100 stars.
user:defunkt	Get all repositories from the user defunkt.
pugs pushed:>2013-01-28	Pugs repositories pushed to since Jan 28, 2013.
node.js forks:<200	Find all node.js repositories with less than 200 forks.
jquery size:1024..4089	Find jquery repositories between the sizes 1024 and 4089 kB.
gitx fork:true	Repository search includes forks of gitx.
gitx fork:only	Repository search returns only forks of gitx.

Code search looks through the files hosted on GitHub. You can also filter the results:

This search	Finds repositories with…
install repo:charles/privaterepo	Find all instances of install in code from the repository charles/privaterepo.
shogun user:heroku	Find references to shogun from all public heroku repositories.
join extension:coffee	Find all instances of join in code with coffee extension.
system size:>1000	Find all instances of system in code of file size greater than 1000kbs.
examples path:/docs/	Find all examples in the path /docs/.
replace fork:true	Search replace in the source code of forks.

Issue search looks through issues and pull requests on GitHub. You can also filter the results:

This search	Finds issues…
encoding user:heroku	Encoding issues across the Heroku organization.
cat is:open	Find cat issues that are open.
strange comments:>42	Issues with more than 42 comments.
hard label:bug	Hard issues labeled as a bug.
author:mojombo	All issues authored by mojombo.
mentions:tpope	All issues mentioning tpope.
assignee:rtomayko	All issues assigned to rtomayko.
exception created:>2012-12-31	Created since the beginning of 2013.
exception updated:<2013-01-01	Last updated before 2013.

User search finds users with an account on GitHub. You can also filter the results:

This search	Finds repositories with…
fullname:"Linus Torvalds"	Find users with the full name "Linus Torvalds".
tom location:"San Francisco, CA"	Find all tom users in "San Francisco, CA".
chris followers:100..200	Find all chris users with followers between 100 and 200.
ryan repos:>10	Find all ryan users with more than 10 repositories.

555	pub trait Sealed {}
556	impl Sealed for super::LittleEndian {}
557	impl Sealed for super::BigEndian {}
558	}
559
560	pub trait ByteOrder: /* ... */ + private::Sealed {
561	// ...
562	}
563	```
564
565	This way, although downstream crates can use this trait, they cannot actually

268	the potential for "sealed" traits to alter this dynamic.)
269
270	#### Minor change: adding a defaulted item.
271
272	Adding a defaulted item is technically a breaking change:
…
740	breaking downstream code.
741
742	**Sealed traits**
743
744	The ability to annotate a trait with some "sealed" marker, saying that no
745	external implementations are allowed, would be useful in certain cases where a

265	allows OIBITs to leak through, and allows specialization to "see" the full type
266	being returned. That is, `impl Trait` does not attempt to be a "tightly sealed"
267	abstraction boundary. The rationale for this design is a mixture of pragmatics
…
335	In the [most recent RFC](https://github.com/rust-lang/rfcs/pull/1305) related to
336	this feature, a more "tightly sealed" abstraction mechanism was
337	proposed. However, part of the discussion on specialization centered on

240	errors. There are reasonable use cases for such functions, for example emulation
241	of sealed traits.
242	The only suspicious part about it is documentation - what arguments can it take