Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Added .NET Innovation sample draft for Generics #407

Closed
wants to merge 1 commit into from

Conversation

kuhlenh
Copy link

@kuhlenh kuhlenh commented Mar 6, 2015

Working on creating educational examples of topical .NET Innovations across the language and runtime. This is my first draft for the Generics example.

@dnfclas
Copy link

dnfclas commented Mar 6, 2015

Hi @kuhlenh, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

**GENERICS**
===================

We use generics implicitly all the time in C#. When you use LINQ in C#, do you notice you are working with <code>IEnumerable\<T\></code>? Ever wonder what <code>T</code> is and what it means?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can just wrap the statements in single backticks instead of wrapping them intags, then you can get rid of escaping the< >` as well.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are plenty of explicit uses of generics, too. List and Dictionary<K,V> have to be among the most popular .NET classes. Also, people do use IEnumberable directly, too.

I'd lead more with the explicit cases of generics being useful and then follow with the implicit cases.

Before generics, everyone was using ArrayList and then casting all the time. That requirement is now gone.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should decide on a good pattern for the title that we can use for the other documents you have planned. I need to think about that a bit. I'm hesitant to pivot on "innovation". Certainly, we built many features that are innovations, however, we'll want the ability to document a feature that doesn't cleanly fit as an "innovation" . It will be an exercise for the reader on which ones were truly innovative at the time they were released.

How about:

.NET Feature: Generics

@richlander
Copy link
Member

@kuhlenh What do you want to do with this PR? Would be good to keep it moving.

@richlander richlander added the documentation Documentation bug or enhancement, does not impact product or test code label Mar 25, 2015
@dnfclas
Copy link

dnfclas commented Apr 28, 2015

@kuhlenh, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, DNFBOT;

@richlander
Copy link
Member

Moving to https://github.com/dotnet/core-docs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Documentation bug or enhancement, does not impact product or test code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants