tree 18864a2278cc91263fe3ff97bb6779bd475cf7f1
parent c3c80f29aca4b8a46e217125bc3753f5229046ac
parent 9785f9ae14eb9aa5b927cdc7236a94d91aa766ed
author bors[bot] <26634292+bors[bot]@users.noreply.github.com> 1578334152 +0000
committer GitHub <noreply@github.com> 1578334152 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJeE3fICRBK7hj4Ov3rIwAAdHIIAG2wym2iAUpFDjrlPxowVKv6
 O0OT8iTNr/ebrVeXQljmuTasdSXIrEbcvarZyNqSAheAWS1QKkJTGcxcthzLy6XQ
 Z4Cw70znEqVL25zYx72IiW9Uc34360FlfgRe60t0nHiaeoe6fUlugHziurchHmfx
 MCx4B/rvCLDrz+VIIxGF4q1zOzeXIfJblhBQXNA3can4nUBXoBLKbj77fItTCOds
 9X+wtPIN8Uo/SIsWwF9wsdZsxOt+oqn7V7HyTTaL0JOYlPobn+8gKexPLSoCJNPH
 w//T6sb9Evz4o/yM48W6EmXBP8R7xqM5TFkux+Vrp72l2fbbTS2742S6dQte6Fk=
 =MbHj
 -----END PGP SIGNATURE-----
 

Merge #127

127: Remove intrinsics r=torfmaster a=torfmaster

# Summary

The error message when not enabling the `#![feature(core_intrinsics)]` feature reads

> use of unstable library feature 'core_intrinsics': intrinsics are unlikely to ever be stabilized, instead they should be used through stabilized interfaces in the rest of the standard library

I think we should - unlike other nightly features which will hopefully be stabilized - not use this unless absolutely necessary. I removed the feature in a straightforward way, however. @jrvanwhy is the expert in that matter.

Co-authored-by: torfmaster <briefe@kebes.de>