Skip to content

links to our type provider talk #327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 7, 2014
Merged

links to our type provider talk #327

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions overviews/macros/typeproviders.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,9 @@ which means that both authors and users of public type providers will have to ad
However, after macro annotations expand, the resulting code will no longer have any references to macro paradise
and won't require its presence at compile-time or at runtime.

Recently we've given a talk about macro-based type providers in Scala, summarizing the state of the art and providing
concrete examples. Slides and accompanying code can be found at [https://github.com/travisbrown/type-provider-examples](https://github.com/travisbrown/type-provider-examples).

## Type providers

Type providers are a strongly-typed type-bridging mechanism, which enables information-rich programming in F# 3.0.
Expand Down