Read Effective Java 3rd Edition by Joshua Bloch, Item 68 for a full discussion. Joshua recommends to prefer primitives over boxed primitives. A few points he makes: *Primitives are more time and space-efficient. *Double equals operator can't be used with Boxed primitives. *Unboxing can result in a NPE. Auto-unboxing happens automatically, for example, when primitives and boxed primitives are mixed in an operation. More on reddit.com

Please ensure that: Your code is properly formatted as code block - see the sidebar (About on mobile) for instructions You include any and all error messages in full You ask clear questions You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions. Trying to solve problems on your own is a very important skill. Also, see Learn to help yourself in the sidebar If any of the above points is not met, your post can and will be removed without further warning. Code is to be formatted as code block (old reddit: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png ) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc. Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit. Code blocks look like this: public class HelloWorld { public static void main(String[] args) { System.out.println("Hello World!"); } } You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above. If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures. To potential helpers Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice. I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns. More on reddit.com

A wrapper is a class or function whose main purpose is to just forward calls to another class or function. The point of a wrapper is so you can use a different interface to access something. There are a couple big reasons to have a wrapper. One use is to simplify the interface. The functions that are part of the Windows API that operate on files, for example, require you to manually check an error code if something goes wrong. The File class wraps those functions and checks the error code for you, converting it into an exception. The Windows API functions also have a lot of optional parameters, but, since they were written in C, which doesn't have function overloading, you have to manually put in null or some default value for all of the optional arguments every time. Since C# supports overloading, the wrapper provides overloads so you don't have to specify the optional arguments. Another thing you'd use a wrapper for is if you want to access an object through an interface that the class doesn't implement. You can write a wrapper class that implements the interface and calls methods on the real object that do whatever operations. For example, Google Drive, Dropbox, and Microsoft OneDrive all have different APIs. If you're writing a program and want to be able to access files from any of them, you'd probably want to write wrappers that all implement the same interface so that you don't have to write all your file access functions three times. There's plenty of other reasons to use a wrapper, but the basic idea is that you're exposing an interface that you want to access something that has a different interface. More on reddit.com

I'm a big fan of this too.

If anyone wants another example, my rateio library does precisely this to provide rate-limiting mechanics for any io-implementor. There's a good example for doing it with net.Conn.

More on reddit.com