Good idea... but...
"Maybe if they made decent and accurate documentation you wouldn't need to use a search engine all the time?"
This... first, I do want to say I actually like the idea of what they are doing here. When you do have to look for some sample code, it would indeed be nicer to have it in the IDE than having to switch between IDE and browser.
That said.... Switching back and forth between Linux, Windows, and Android programming...
The typical libraries on a Linux system (GTK, SDL, C library, X, XML lib if you're doing that, and so on) have reasonably good documentation, and usually code snippets that actually follow recommended programming practices. There's generally one particular library (with a fairly stable API over the course of a decade or more) to get any particular job done (although other libs may exist, they won't be installed by default, and it'll be pretty clear looking online which lib to use if your goal is to program for a "stock" system.) There still *is* Google pulling up snippets on stackoverflow etc. if you need it, but you may actually not need it.
Android, the whole API is there; not good code samples but honestly most of the API is quite straightforward -- including what API version a given call was introduced, if it was deprecated and if so what API version it was deprecated (and there's a table mapping API version to version of Android.) There's a chance that you may not have to google anything. I wrote one app without googling a thing, and a second app I only had to look up something (undocumented) on handling the status bar.
Windows? There's certainly extensive docs, but the APIs (for most functions) seem overcomplicated, no indication of what the recommended way is to use these APIs, and usually mutliple APIs with no indication on even *which* API to use (sometimes Microsoft deprecates one, but programmers find the replacement inadequate and say "don't use the replacement, use the deprecated one"). Sometimes, Microsoft has just left docs online, no header or footer to indicate "this is no longer up to date", I'll be reading up on something just to realize "Hey, this is from 2008, and this API has already been replaced twice since then." And, there'll be a high-level API that covers like 90% of functionality, then you've got to dig down to a lower-level API to do the rest -- not for unusual actions but for actions that every user of the APi wants to perform. In a few cases, I find they reimplemented some functionality (usually fixing bugs and speeding it up) but, despite the same functionality (or a superset of the old functionality), same inputs, and same outputs, the API calls will all be different (I think because they just had someone write the new API from scratch and it simply didn't occur to them to make it compatible with the old one.) It's honestly confusing as all hell. And, unfortunately, I've found plenty of code on stackoverflow, etc., that although it may have worked, appeared even at a glance to be quite fragile (for example, a snippet to print a temporary PDF file that would pause 1 second and just *assume* the print job had finished (deleting the temp file), instead of actually CHECKING if the print job had finished first.)